Networking Forums

Go Back   Networking Forums > Networking Newsgroups > Network Routers
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Network connectivity problem

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 07-28-2004, 02:55 PM
 
DaveL


I have two servers which communicate with each other over a T1. ServerA
intermittently loses communication with serverB. I can re-establish the
connection by rebooting serverA. But serverA never has a problem
communicating with any other server, just serverB.

So the users call me up and say it's doing it again. I told them to hold
off rebooting until I can look at serverB. Sure enough, serverB cannot ping
serverA. It can, however ping serverA's gateway (192.168.75.253). I have
someone run a tracert from serverA to serverB and the first line is
192.168.75.254. But shouldn't that have been 253?

So I have them reboot serverA and communication is reestablished. I have
them do another tracert and now the 1st line has the ip host address of
253! What is going on? Before the reboot it was trying to route through
254 and after a reboot it goes back to the proper 253. Would made it
change? Is there a problem with 253 so that it has to defer to 254?

Thanks,
DaveL

Reply With Quote
  #2  
Old 09-24-2004, 11:13 PM
 
Kaptain Krunch
Default Re: Network connectivity problem



could be a flaky net card, or is this through a router and internet
connection or IC sharing...???

What is changing the address is DHCP is assinging a new addy if it cant get
through the other one.. try using static addys for a while and see what
happens

KK

"DaveL" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have two servers which communicate with each other over a T1. ServerA
> intermittently loses communication with serverB. I can re-establish the
> connection by rebooting serverA. But serverA never has a problem
> communicating with any other server, just serverB.
>
> So the users call me up and say it's doing it again. I told them to hold
> off rebooting until I can look at serverB. Sure enough, serverB cannot

ping
> serverA. It can, however ping serverA's gateway (192.168.75.253). I have
> someone run a tracert from serverA to serverB and the first line is
> 192.168.75.254. But shouldn't that have been 253?
>
> So I have them reboot serverA and communication is reestablished. I have
> them do another tracert and now the 1st line has the ip host address of
> 253! What is going on? Before the reboot it was trying to route through
> 254 and after a reboot it goes back to the proper 253. Would made it
> change? Is there a problem with 253 so that it has to defer to 254?
>
> Thanks,
> DaveL
>



Reply With Quote
Reply

Networking Forums > Networking Newsgroups > Network Routers


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 07:19 PM.

Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.