![]() |
![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|
|||
|
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 |
|
#2
|
|||
|
|
|||
|
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 > |