Ping & DHCP Problem

  • Thread starter Thread starter Ron
  • Start date Start date
R

Ron

I have a home network that has been working fine until yesterday. I
have a W2K server working as DHCP & DNS. I am using a Netgear router
on my network. Yesterday I lost the ability of any computers to ping
or "see" the server. All computers can successfully obtain an IP
address from the server but unable to ping the server. The server can
ping 127.0.0.1 and its private address 192.168.254.50 but unable to
ping any other computers or the router. Other computers can ping the
router successfully. The server also cannot get out to the internet
(probably due to not being able to "see" the router)

I then switched cables and router ports for the server without any
change. I then changed the router to be the DHCP server, turned off
DHCP on the W2K server, and the W2K server was able to obtain an
address but unable to ping the router (now DHCP).

Does this sound like a bad NIC or something else within W2K server?
 
:
: I have a home network that has been working fine until yesterday. I
: have a W2K server working as DHCP & DNS. I am using a Netgear router
: on my network. Yesterday I lost the ability of any computers to ping
: or "see" the server. All computers can successfully obtain an IP
: address from the server but unable to ping the server. The server can
: ping 127.0.0.1 and its private address 192.168.254.50 but unable to
: ping any other computers or the router. Other computers can ping the
: router successfully. The server also cannot get out to the internet
: (probably due to not being able to "see" the router)
:
: I then switched cables and router ports for the server without any
: change. I then changed the router to be the DHCP server, turned off
: DHCP on the W2K server, and the W2K server was able to obtain an
: address but unable to ping the router (now DHCP).

More info:

Ping workstation and ping router is not clear. Ping workstation by IP/Name,
etc. is more informative.
Switched cables and router ports means? You replaced the cables or you
switched with ones that were working on the workstations? Difference is, if
you used different cables, not already in the equation, how do you know
they're good?
You switched router ports... to ones that were working or open ports. Are
all ports set the same?
Is full duplex enabled on the server NIC? If so, what happens if you set it
manually to half-duplex 10/100?
Tell us about the DNS if not pinging by name and showing ipconfig /all for
server and one workstation might be beneficial.

--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
-Technet Knowledge Base-
http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto&sd=TECH&ln=EN-US&FR=0
-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-WSH 5.6 documentation download-
http://www.microsoft.com/downloads/...48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en
-MSDN Library-
http://msdn.microsoft.com/library/default.asp
 
Roland Hall said:
:
: I have a home network that has been working fine until yesterday. I
: have a W2K server working as DHCP & DNS. I am using a Netgear router
: on my network. Yesterday I lost the ability of any computers to ping
: or "see" the server. All computers can successfully obtain an IP
: address from the server but unable to ping the server. The server can
: ping 127.0.0.1 and its private address 192.168.254.50 but unable to
: ping any other computers or the router. Other computers can ping the
: router successfully. The server also cannot get out to the internet
: (probably due to not being able to "see" the router)
:
: I then switched cables and router ports for the server without any
: change. I then changed the router to be the DHCP server, turned off
: DHCP on the W2K server, and the W2K server was able to obtain an
: address but unable to ping the router (now DHCP).

More info:

Ping workstation and ping router is not clear. Ping workstation by IP/Name,
etc. is more informative.
Click to expand...
I pinged by IP. No response
Switched cables and router ports means? You replaced the cables or you
switched with ones that were working on the workstations?
Click to expand...
I had an unused port that I knew was working (both cable and port)
Difference is, if
you used different cables, not already in the equation, how do you know
they're good?
You switched router ports... to ones that were working or open ports. Are
all ports set the same? See above
Is full duplex enabled on the server NIC? If so, what happens if you set it
manually to half-duplex 10/100?
Click to expand...
Did not try this.....
Tell us about the DNS if not pinging by name and showing ipconfig /all for
server and one workstation might be beneficial.
Click to expand...
Not necessary. Spent $7 on a new nic for the server and all problems
solved. Seems the nic was bad. As learned years ago. Start with the
most inexpensive thing first. Additionally, without configuration
changes, connectivity problems are nearly 99% the cause of
hardware/connection failures. This approach once again worked to
solve my problem
--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
-Technet Knowledge Base-
http://support.microsoft.com/default.aspx?scid=fh;EN-US;kbhowto&sd=TECH&ln=EN-US&FR=0
-Technet Script Center-
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/scriptcenter/default.asp
-WSH 5.6 documentation download-
http://www.microsoft.com/downloads/...48-207D-4BE1-8A76-1C4099D7BBB9&displaylang=en
-MSDN Library-
http://msdn.microsoft.com/library/default.asp
Click to expand...

Roland,

Thanks for your response.
 
:
: Not necessary. Spent $7 on a new nic for the server and all problems
: solved. Seems the nic was bad. As learned years ago. Start with the
: most inexpensive thing first. Additionally, without configuration
: changes, connectivity problems are nearly 99% the cause of
: hardware/connection failures. This approach once again worked to
: solve my problem

I'm surprised the NIC was the issue, unless it was the connector on the NIC
since pinging localhost worked.
Hardware issues are sometimes the trial/error method. Glad you got it
solved.

: Roland,
: Thanks for your response.

You're welcome. Thanks for the follow up.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp
 
Back
Top