pugdog_fan
asked on
Microsoft Server 2003 ... clients cannot PING by IP or name ... but server is working 100% (probably a simple fix) (see Q: for loads of details) ...
Windows 2003 server
IP address 192.168.1.3/24
NetBIOS name: appraisal2
Server is Domain Controller, DNS, and DHCP (all 3 services started and running) ....
The server had a 'power outage' and had to be started up from an powered OFF state this morning.
The Internet access is here is cable, and the Netgear 'router' is at IP 192.168.1.1.
Right now, the server can ping all clients on the LAN by name and IP (about 7 or 8 PCs and a few printers). The server can can ping out to the Internet by name and/or IP address. Things seem to be working fine from the server side.
The client machines boot up, get their IP from the above server, and then can log into the domain (again via the server above). The clients cannot get out to the Internet (neither by name or IP address). The can ping each other, but no client can PING 192.168.1.3. If they try, it will time out. This is strange in itself because this has always worked (prior to the power outage). There is 'nothing' running on the server to prevent this (because it was working prior to the power outage.
If I 'change' the DNS setting from obtain automatically, and hard code it in as 192.168.1.1 (which is the Netgear router), the clients can then at least get out to the Internet (by name or number) ... but they cannot reach 192.168.1.3 by name or IP address.
This seems really simple and basic on face value.
I've tried stopping and restarting all services (DNS, DHCP, etc.). I've checked the event viewer, and there is nothing outstanding in any of the log files. Things look 'clean' on the face.
I tried to 'rebuild' TCP/IP with the netsh int reset command, but that was not the fix. I've restared (and cut off power) a few times to the server.
I've turned off all printers and computers, and then I restarted them AFTER the server was up and running.
I'm not sure what to try next.
Clients can ping each other, they can ping the Netgear gateway, but they simply cannot reach the server at 192.168.1.3 (by name or IP). I've tried changing the IP address on the server to 192.168.1.33, and the results were the same.
I've cut off the power to the switch involved, the Netgear router, the Internet ISP 'router box' ... and all computers and printers.
To me, it seems like something might have been 'broken' with the DNS software on the server.
Re-CAP: All was working fine ... the workers came in to a power outage on the server ... once the server was restarted, this state of affairs was the result.
Any tips, suggestions, or advice would be greatly appreciated.
IP address 192.168.1.3/24
NetBIOS name: appraisal2
Server is Domain Controller, DNS, and DHCP (all 3 services started and running) ....
The server had a 'power outage' and had to be started up from an powered OFF state this morning.
The Internet access is here is cable, and the Netgear 'router' is at IP 192.168.1.1.
Right now, the server can ping all clients on the LAN by name and IP (about 7 or 8 PCs and a few printers). The server can can ping out to the Internet by name and/or IP address. Things seem to be working fine from the server side.
The client machines boot up, get their IP from the above server, and then can log into the domain (again via the server above). The clients cannot get out to the Internet (neither by name or IP address). The can ping each other, but no client can PING 192.168.1.3. If they try, it will time out. This is strange in itself because this has always worked (prior to the power outage). There is 'nothing' running on the server to prevent this (because it was working prior to the power outage.
If I 'change' the DNS setting from obtain automatically, and hard code it in as 192.168.1.1 (which is the Netgear router), the clients can then at least get out to the Internet (by name or number) ... but they cannot reach 192.168.1.3 by name or IP address.
This seems really simple and basic on face value.
I've tried stopping and restarting all services (DNS, DHCP, etc.). I've checked the event viewer, and there is nothing outstanding in any of the log files. Things look 'clean' on the face.
I tried to 'rebuild' TCP/IP with the netsh int reset command, but that was not the fix. I've restared (and cut off power) a few times to the server.
I've turned off all printers and computers, and then I restarted them AFTER the server was up and running.
I'm not sure what to try next.
Clients can ping each other, they can ping the Netgear gateway, but they simply cannot reach the server at 192.168.1.3 (by name or IP). I've tried changing the IP address on the server to 192.168.1.33, and the results were the same.
I've cut off the power to the switch involved, the Netgear router, the Internet ISP 'router box' ... and all computers and printers.
To me, it seems like something might have been 'broken' with the DNS software on the server.
Re-CAP: All was working fine ... the workers came in to a power outage on the server ... once the server was restarted, this state of affairs was the result.
Any tips, suggestions, or advice would be greatly appreciated.
do a nslookup hostname
check if you have firewall turned on on your server.
check if you have firewall turned on on your server.
ASKER
I double-checked the DHCP settings ... they were still correct. I even removed them and put them back in. I restarted the server ...
No nslookup concern here ...
No firewall running on server.
NOW .... it seems even DHCP is failing ...
I now have a cross-over cable running from the server to my own laptop. My laptop is NOT pulling an IP address from the server.
I put in a static IP on my laptop. My laptop CANNOT ping the server by its name and/or IP.
The server CAN ping my laptop by its name and/or IP address.
This is really strange.
No nslookup concern here ...
No firewall running on server.
NOW .... it seems even DHCP is failing ...
I now have a cross-over cable running from the server to my own laptop. My laptop is NOT pulling an IP address from the server.
I put in a static IP on my laptop. My laptop CANNOT ping the server by its name and/or IP.
The server CAN ping my laptop by its name and/or IP address.
This is really strange.
ipconfig/all on your laptop, then post the result
ASKER
If I have my laptop setup for DHCP .... it now FAILS to get an IP from the server ....
I have to manually set a static IP on my laptop of:
laptop:
192.168.1.5
255.255.255.0
192.168.1.1
server:
192.168.1.3
255.255.255.0
192.168.1.1
The laptop CANNOT ping the server by IP or name, but the server CAN ping my laptop by either IP or name.
--------------------
For the 1st time in over 20 years, I am contracting with a company who is a GOLD partner with Microsoft. In about 30 min., I'll have the PIN# and 800 number (special HOT line) to Microsoft ...
I finally get to call the "mothership" for support.
I've never had to do this before, so I'll post the results of this after the call.
Hopefully, they will be able to remote into the server (because I've put it back online with its original cable), and it can now get out to the Internet, etc.
I'll update you all in a bit.
I have to manually set a static IP on my laptop of:
laptop:
192.168.1.5
255.255.255.0
192.168.1.1
server:
192.168.1.3
255.255.255.0
192.168.1.1
The laptop CANNOT ping the server by IP or name, but the server CAN ping my laptop by either IP or name.
--------------------
For the 1st time in over 20 years, I am contracting with a company who is a GOLD partner with Microsoft. In about 30 min., I'll have the PIN# and 800 number (special HOT line) to Microsoft ...
I finally get to call the "mothership" for support.
I've never had to do this before, so I'll post the results of this after the call.
Hopefully, they will be able to remote into the server (because I've put it back online with its original cable), and it can now get out to the Internet, etc.
I'll update you all in a bit.
sorry, i need to see ipconfig/all
this should be a simple problem to solve. firewall, antivirus crap are the common cause. another is the DNS server setting wrong.
this should be a simple problem to solve. firewall, antivirus crap are the common cause. another is the DNS server setting wrong.
ASKER
Hi PaperTiger:
I mentioned to you, my laptop is not getting its IP information from the server ... I 'hard coded' it in manually (static).
There is nothing to post with ipconfig /all other then what I already gave you.
I mentioned to you, my laptop is not getting its IP information from the server ... I 'hard coded' it in manually (static).
There is nothing to post with ipconfig /all other then what I already gave you.
i know. when you hard code it, what did you put under DNS?
ASKER
192.168.1.3
My IP is: 192.168.1.5
My subnet is: 255.255.255.0
My gateway is: 192.168.1.1 (which I know is not reachable)
DNS is 'hard' coded as: 192.168.1.3
The server is:
IP: 192.168.1.3
subnet: 255.255.255.0
gateway: 192.168.1.1
DNS: 192.168.1.3
My IP is: 192.168.1.5
My subnet is: 255.255.255.0
My gateway is: 192.168.1.1 (which I know is not reachable)
DNS is 'hard' coded as: 192.168.1.3
The server is:
IP: 192.168.1.3
subnet: 255.255.255.0
gateway: 192.168.1.1
DNS: 192.168.1.3
OK, the problem is pretty simple and can only be a few reasons:
ping IP address
1. Try to ping the router 192.168.1.1 - this must work, if not:
a. check wire and cable.
b. check any firewall/AV on the laptop is blocking the ping
2. Try to ping the server with the IP address, if not work and 1 works:
a. check any firewall/AV on the server
b. check any firewall/AV on the laptop
ping IP address
1. Try to ping the router 192.168.1.1 - this must work, if not:
a. check wire and cable.
b. check any firewall/AV on the laptop is blocking the ping
2. Try to ping the server with the IP address, if not work and 1 works:
a. check any firewall/AV on the server
b. check any firewall/AV on the laptop
ASKER
No firewall software or AV s/w on server ...
This server was working just fine yesterday (prior to the power outage).
When the power went out ... all other computers came back on when the power was restored ...
This server had to put cut back on manually, and when they did .... the results of the problem came up.
This server was working just fine yesterday (prior to the power outage).
When the power went out ... all other computers came back on when the power was restored ...
This server had to put cut back on manually, and when they did .... the results of the problem came up.
does 1 work?
ASKER
Of course it works!
I said it worked in my main 1st reply. I've said I've been able to ping the gateway (and even get out to the Internet) if I switch my clients to this IP.
The problem here is 100% related to some services (software) running on the server.
I am 1000% sure of this.
I said it worked in my main 1st reply. I've said I've been able to ping the gateway (and even get out to the Internet) if I switch my clients to this IP.
The problem here is 100% related to some services (software) running on the server.
I am 1000% sure of this.
i have had similar problem one time. it's related to network driver on the server. Once in a blue moon, it would behave like that - one way traffic. can ping from the server, but not to the server. only a reboot can fix that.
i ended up updating the network driver to the latest one. never had the problem since.
give it a shot.
i ended up updating the network driver to the latest one. never had the problem since.
give it a shot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you verifed everything defined in the DHCP scope is correct and getting to the client? Did the server turn on Windows Firewall on that connection? Is Routing and Remote access being used at all?