Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Strange routing problem?

0 views
Skip to first unread message

Rich Stevenson

unread,
Jan 12, 2004, 5:25:56 PM1/12/04
to
Forgot to mention that that the ip address was changed on this server and
I've removed and reinstalled DS to resolve previous -634 erros that kept
returning.

"Rich Stevenson" <RichStevenson@NO_HABLO_SPAMO.ZoomInternet.net> wrote in
message news:W3FMb.12180$VM1...@prv-forum2.provo.novell.com...
> I was told in the adminn tools forum to post in the ds forum, but I've
> resolved my ds errors. I'm posting here because no it seems like an tcpip
> issue, maybe...
> Here's what I've got, all servers are NW6SP3....
> In a WAN environment I have one server across the WAN that has been
running
> fine. I can hit any of it's web services i.e. Apache & Management portal.
I
> now have a new server setup in the same location and although time is in
> sync and no communication errors checking with dsrepair, I can't hit
Apache
> or the Management Portal.
> Here's the strange part, for me anyway...
> If I have someone who's logged in on the same segment where the server
> resides, they can hit everything fine. So it's just when we're on another
> segment that we can't hit those services. We can ping back and forth from
> server to server though. Now from home I log into our Cisco VPN
> concentrator, which is the same concentrator that links our offices across
> the WAN, I can hit those services from here. One thing I know for sure is
> the packet is getting there it just doesn't seem to be getting back. I say
> this because at one point I had bordermanager running on the problem
server
> and my browser didn't seem to be hitting the http proxy service. But when
I
> looked at the proxy logs it showed that the ACL's granted access to the
> website I was requesting. I also did a packet trace from my workstation
and
> tried to hit the portal. I saw my request go out for port 8008, saw the
> redirection to 8009 and then got a reply that the checksum was incorrect.
> Can anybody shed some light on this for me?
> Thanks
>
>


Rich Stevenson

unread,
Jan 12, 2004, 5:19:34 PM1/12/04
to

Donald Albury

unread,
Jan 12, 2004, 6:11:26 PM1/12/04
to
On Mon, 12 Jan 2004 22:25:56 GMT, "Rich Stevenson"
<RichStevenson@NO_HABLO_SPAMO.ZoomInternet.net> wrote:

>Forgot to mention that that the ip address was changed on this server and
>I've removed and reinstalled DS to resolve previous -634 erros that kept
>returning.

Did you catch everything that is listed in TID 10067853
(http://support.novell.com/cgi-bin/search/searchtid.cgi?/10067853.htm)?

Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

Rich Stevenson

unread,
Jan 13, 2004, 7:15:36 AM1/13/04
to
Yep. Triple checked it too.

>>> Donald Albury<dalbury@not_bellsout.net> 1/12/2004 6:11:26 PM >>>

Donald Albury

unread,
Jan 13, 2004, 7:08:13 PM1/13/04
to
On Tue, 13 Jan 2004 12:15:36 GMT, "Rich Stevenson"
<RichStevenson_NO_@_SPAM_.ZoomInternet.net> wrote:

>Yep. Triple checked it too.

How about SLP? Does the SLP.CFG file on the server point to the DA?
Is SLP loaded on the server? What are the results of 'display slp
services' on the server console?

I don't think web services are dependent on SLP, but the behavior you
describe of services being available on the local segment, but not
from another segment, sounds like an SLP problem.

Rich Stevenson

unread,
Jan 14, 2004, 7:41:18 AM1/14/04
to
Yep. SLP is working correctly. The DA is across the WAN and it regisiters
just fine. If I type display slp services on the problem server I can see
all of the services available from the DA. One more thing I just noticed...I
tried to simply hit the default Apache page, the one served up on port 80.
That page, which is just the frameset, comes down after a few minutes. But
the pages that are supposed to fill the frames timeout. So, it looks like
the packets are coming back, just very very slowly causing it to time out.

>>> Donald Albury<dalbury@not_bellsout.net> 1/13/2004 7:08:13 PM >>>

Rich Stevenson

unread,
Jan 14, 2004, 9:34:23 AM1/14/04
to
Ok we got it going now. The server is using the Q57 driver and the tcpip
stack doesn't play well with it, thus the checksum errors in the trace.
Upgraded to the latest stack and everything works now. Thanks for your
help.

>>> Rich Stevenson<RichStevenson_NO_@_SPAM_.ZoomInternet.net> 1/14/2004
7:41:18 AM >>>

Donald Albury

unread,
Jan 14, 2004, 1:46:39 PM1/14/04
to
On Wed, 14 Jan 2004 14:34:23 GMT, "Rich Stevenson"
<RichStevenson_NO_@_SPAM_.ZoomInternet.net> wrote:

>Ok we got it going now. The server is using the Q57 driver and the tcpip
>stack doesn't play well with it, thus the checksum errors in the trace.
>Upgraded to the latest stack and everything works now. Thanks for your
>help.

It doesn't look like I was much help. Anyway, glad you got it sorted.

0 new messages