|
Answer» I suspect (hope) I'm missing something obvious and simple. The computer giving me fits is a Dell Poweredge 1950. I have no reason to believe that hardware is the problem because it was working fine UNTIL the OS was upgraded from Windows Server 2003 R2 to Windows Server 2008.
After Server 2008 was installed the server was rejoined to the domain. It can see and access other computers on the local network. It can not access the Internet. Windows firewall and IE Enhanced security are disabled. DNS and the default gateway match everything else on the network. I TRIED assigning a static IP as well as allowing DHCP to assign an IP. This server can not ping anything OUTSIDE the LAN.
There is another system on the network already running Server 2008 (my workstation). It connected to the domain and the Internet with no issues. I compaired the network settings of the server and my workstation and they appear identical.
I've tried with and without IPv6.
I've disabled and enable the NIC several times. Attempts to repair the network connection have not succeeded.
No roles have been added to the "bad" server.
I installed the latest DRIVERS for the NIC.
My brain is oozing out of my ears! Anyone have any idea? Help!
No replies? I'm feeling doomed . . . .
UPDATE: When I ping the local network I get the usual reply.
Ping NVICSRV01
Pinging nvicsrv01.nvicorp.local [10.1.1.253] with 32 bytes of data: Reply from 10.1.1.253: bytes=32 time<1ms TTL=128 Reply from 10.1.1.253: bytes=32 time<1ms TTL=128 Reply from 10.1.1.253: bytes=32 time<1ms TTL=128
Ping statistics for 10.1.1.253: Packets: Sent = 4, received =4, Lost = 0 (0% loss), Approximate round trip times in mili-seconds: Minimum = 0MS, MAXIMUM = 0ms, Average = 0ms
No problem there. When I attempt to ping something on the Internet, Google for instance:
Ping www.google.com
Pinging www.1.google.com [64.233.167.147] with 32 bytes of data: Request time out. Reply from 10.1.1.37: Destination host unreachable. Reply from 10.1.1.37: Destination host unreachable. Request timed out.
Ping statistics for 64.233.167.147: Packets: Sent = 4, Received = 2, Lost =2 (50% loss).
I'm still at a loss. Is 10.1.1.37 your router?10.1.1.37 is the IP of the server sending the ping.
We are able to give the server Internet access by setting its Default Gateway to the IP of our firewall (hardware). This server (a Dell PowerEdge1950) is the only computer on our network that requires this; not even another system running Server 2008 has the issue.
Why is this thus? What is the reason for this thusness? We know not. When you give it the default gateway of your router (not the firewall, the actual gateway/bridge/router/whatever that is connected to your cable modem/DSL modem/T1 CSUDSU/whatever), it can't get on the net?You are correct, sir. If this server is assigned the same default gateway as the rest of the network, it can't get to the Internet. If the IP of the firewall is set as the default gateway, the server can get to the Internet. Hmmm...
Just for ****s and giggles, do you have an extra NIC to test with?Server has 2 NICs. Same result with either.
|