- Bizarre DHCP problem
- Posted by ZB on July 25th, 2003
Hi All
I used to have 2 comps on a home LAN.
Linksys BESFR41 router with 4 switch ports, one PC running win2k and a
laptop running win98. I bought a new pc with xp pro and connected it to the
same LAN port as the win2k machine. It works fine. I have moved the old PC
to the bedroom which has a rj45 socket wired back to the linksys router.
For some reason the XP & laptop work fine but the win2k machine refuses to
get an IP address. It has a working physical connection back to the router
because the status lights are on both on the router and the network card of
the PC. However, I cannot ping the router and despite restarting the router,
PC etc, I still cant get anything other than a self configured & useless 169
address.
Checked out the router config and there is nothing in DHCP which suggests
there should be a problem.
Any suggestions??? TIA
- Posted by Jeffrey Edwards on July 25th, 2003
Manually set a static ipaddress and mask for the 2k machine. Ping the other
pc's. If you can ping then you've verified that communication is good.
Remove the static configuration and save the changes. Go to Start/Run and
type CMD to get to a command prompt.
Type in ipconfig /all. You should see the default 169.254.x.x address.
Then type is ipconfig /renew. This will send out a broadcast request for
dhcp services. Unfortunately you can not determine from your router if a
request is being made. Hopefully it replies.
Verify that your NIC setting are compatible. Sometimes I've seen issues
with "Auto" selected for the speed and duplexing.
Worst case, statically set an ipaddress, a subnet mask, a default route, and
a DNS server in your tcp/ip properties for your network configuration on the
Win2k server.
Also, make sure that you did not setup the Win2k server to issue DHCP
itself.
--
Jeffrey Edwards
CNE5,CDE,MCP2k,CCA1.8
"ZB" <ZB@hotmail.com> wrote in message
news:bfrmho$i7bt8$1@ID-66527.news.uni-berlin.de...
- Posted by PJB on July 25th, 2003
"ZB" <ZB@hotmail.com> wrote in message
news:bfrmho$i7bt8$1@ID-66527.news.uni-berlin.de...
A friend had a similar problem, which turned out to be a
faulty cable. It had tested ok before it went through the
walls, but became faulty after being stapled too tightly to
the wall.
Easiest to prove things, is to bring the pc nearer the
router and try a different cable.
P.
- Posted by ZB on July 25th, 2003
"ZB" <ZB@hotmail.com> wrote in message
news:bfrmho$i7bt8$1@ID-66527.news.uni-berlin.de...
Thanks for all suggestions, faulty cable despite the lights being green.
- Posted by Billh on July 26th, 2003
Glad it worked. I know the first time I had a bad cable I pulled my hair
out doing all kinds of stuff with the network settings because I "know" I
had a connections the lights where on the nic. Dropped a new cable in and
all was well.
BTW in my case at work I have to deal with up to three bad cables per
computer. One to the wall. The wire in the wall. The cable to jump from
the wire panel in the closet to the switch.
"ZB" <ZB@hotmail.com> wrote in message
news:bfs62j$ijjhf$1@ID-66527.news.uni-berlin.de...
- Posted by Meat Plow on July 26th, 2003
On Fri, 25 Jul 2003 17:40:30 +0100, ZB wrote:
Check the DHCP client on the W2K box. Is it running in services?
