This is a problem that has been plaguing us for years. We schedule a weekly reboot of our windows 2000 servers. About every other weekend, one or two servers (out of ten total) will come back from a reboot but will not be connected to the network. You can log on to the server, and there are no error messages. The only thing wrong is there is no access to the network from the server...and you can't access the server from the network either. The only solution we have is to reboot the servers that don't hook up to the network once more and then typically they connect. I have tried every trick in the book to get our network router and hub running to spec. I have also staggered the reboot times so that the network isn't being "flooded". All of the servers run standalone, they are not on a windows domain. I can't figure out what to tweak or do about this problem.

[Reply or follow-up to this message]

Please supply more info for the servers that do not connect  a) how do they get their 
ip addr?  (static or dhcp) b) if via dhcp where is the dhcp server?  c) run ipconfig 
/all and report all info  d)  if static, can you run ping to its own ip addr successfully? 
 e) you said it's 1 or 2 that do not connect, are they same servers week-to-week? 
 f)  have you done a "reset tcp" ?  looked into it?
I can't say that the forum can find the soln but this data will help.
HTH and maybe give you some food for thought.
Outofpocket

[Reply or follow-up to this message]

On Tuesday, May 27, 2008 at 9:21 am, outofpocket wrote:
>Please supply more info for the servers that do not connect a) how do they get their ip addr? (static or dhcp) static b) if via dhcp where is the dhcp server? see above c) run ipconfig
>/all and report all info I've xx'd out some of the external addresses for security reasons: Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : S03 Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter VestcomLan: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-06-5B-F7-21-86 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.26.56 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.238 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.53 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.14 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.13 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.54 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.57 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.55 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.50 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.69 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.52 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : 192.168.26.51 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.26.1 DNS Servers . . . . . . . . . . . : nnn.nnn.nnn.nnn nnn.nnn.nnn.nnn PPP adapter {EF710DEB-8F43-4714-8087-0C76E04572C4}: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.234.235 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled d) if static, can you run ping to its own ip addr successfully? Yes e) you said it's 1 or 2 that do not connect, are they same servers week-to-week? No it can vary. f) have you done a "reset tcp" ? looked into it? No, I am not familiar with that. Can you elaborate what it does? and the after effects?

[Reply or follow-up to this message]

I don't see anything amiss in the ip scheme you have.   TCP reset is basically the 
same as what's in the following link and resets the TCP stack (you will have to modify 
the new TCP to work as you have them set now)
http://support.microsoft.com/kb/299357 
 I think the syntax for the "reset" part is "reset all"  check around on the net 
and it will clear up.  I have used it and it works ok.  HTH.
Outofpocket

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum