Assigning Static IP Disconnects Network

February 3, 2010 at 19:15:04
Specs: Server 2003 SP2, Xeon quad core 4GB ram
Attempting to assign Static IP to replacement DC, 192.168.10.1 Subnet 255.255.255.0 Gateway 192.168.1.1. Same settings as previous DC with Server 2000. Now I get message "The default gateway is not on the same subnet segment (subnet) that is defined by the IP address and subnet mask". But it is! If I click okay, I loose all network connectivity. Any insight would be appreciated.

See More: Assigning Static IP Disconnects Network

Report •

#1
February 3, 2010 at 20:59:53
No it isn't. The subnet of the DC is 192.168.10. The gateway is on the 192.168.1 subnet, assuming you are using the same subnet mask on the gateway.

Two different subnets. What is the subnet mask on the gateway? If it is the same, try using 192.168.1.10 on the DC if that IP isn't in use anywhere else.


Report •

#2
February 4, 2010 at 16:22:31
Please pardon my fopaux! In my despair to resolve network connectivity I did enter the wrong IP. Earlier I had entered the correct IP which still resulted in no connectivity without the warning. Which is where I stand now. IP 192.168.1.10 Subnet 255.255.255.0 Gateway 192.168.1.1 . Subnet mask on gateway is also 255.255.255.0 . Although Server 2003 indicates that it is connected, it refuses to pass any packets. Hardware is new with two onboard Intel 1000 Pro ports (only using one). After much brainstorming I am satisfied that I probably have a NIC driver issue. Any more thoughts? Thanks in advance!

Report •

#3
February 4, 2010 at 16:58:15
If a nic driver issue you should see it in Device Manger with the yellow exclaimation point.

can you ping loopback 127.0.0.1 ?
if so tcp/ip is fine.

what is the nic connected to?
cable tested as good?


Report •
Related Solutions


Ask Question