Networking issue that is wierd!!!

[Rod]

Maybe you guys and gals can help me out here! I posted
this in Networking group and got "0" replies.

Hey everyone,

This has kinda stumped me. I've never seen this happen
before? I've got a home network setup with a wireless
router using DHCP within the router. Typical settings in
the router,...192.168.1.1 home and then it farms out ip's
based on that. For some damm reason my desktop PC
continues to get a auto ip address issued to it?
169.xxx.xxx.xxx. I've verified all the setting on other
PC's on my network and they are all correct? As a matter
of fact, the PC in question actually see's the network and
shows a 100mb connection! It's a wired connection on the
PC in question, sorry.
Anyhow, I just can't figure out why it won't get an IP
from the Router and keeps assigning itself an auto IP
range address? The PC in question is setup to accept a
DHCP address from the router (no IP statically assigned)
and no DNS statically assigned either. Really Wierd!

Any help or question would be appreciated and answered
quickly! I'm working this issue as we speak!

Thanks,
Rod

..

 

[Kevin D. Goodknecht]

In

Maybe you guys and gals can help me out here! I posted
this in Networking group and got "0" replies.

Hey everyone,

This has kinda stumped me. I've never seen this happen
before? I've got a home network setup with a wireless
router using DHCP within the router. Typical settings in
the router,...192.168.1.1 home and then it farms out ip's
based on that. For some damm reason my desktop PC
continues to get a auto ip address issued to it?
169.xxx.xxx.xxx. I've verified all the setting on other
PC's on my network and they are all correct? As a matter
of fact, the PC in question actually see's the network and
shows a 100mb connection! It's a wired connection on the
PC in question, sorry.
Anyhow, I just can't figure out why it won't get an IP
from the Router and keeps assigning itself an auto IP
range address? The PC in question is setup to accept a
DHCP address from the router (no IP statically assigned)
and no DNS statically assigned either. Really Wierd!

Any help or question would be appreciated and answered
quickly! I'm working this issue as we speak!

Thanks,
Rod

.

Download the netdiag tool from Microsoft an run netdiag /v from the client.
http://www.microsoft.com/downloads/...FamilyID=AAE64B62-27C0-4523-8AF9-66A968A8C942

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
--
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

 

[NT Canuck]

router using DHCP within the router. Typical settings in
the router,...192.168.1.1 home and then it farms out ip's
based on that. For some damm reason my desktop PC
continues to get a auto ip address issued to it?
169.xxx.xxx.xxx. I've verified all the setting on other
PC's on my network and they are all correct?

below only applies if you have no solution...

1. the 169.x address is assigned by the windows system
when it detects a network card...but no service active/found.

2. the windows OS detects/intitiates networking during the
Bootup sequence and your "drivers" may_not be getting
activated/installed until after desktop appears. (maybe)

3. setting a fixed IP for client unit should alleviate above.
(DHCP will constantly_send arp's looking for new_clients,
usually about every 10 seconds..depending on range
of ip's marked/created in the router (check w/sniffer)).
DHCP can allow (?) units nearby to piggyback your
connection...sort of a public accessible network.
http://wigle.net/gps/gps/GPSDB/onli...5009455&lat2=37.6749886325&long2=-122.3750915

4. option is to disable network connection before shut down
and reactivate network after desktop gui (reboot) is done.
control panel/network/ make shortcut to desktop
Windows 2k/xp/net/server can do this "on the fly" (on/off)

--
'Seek and ye shall find'
NT Canuck
http://ntcanuck.com BIND-PE & DNS
http://ntcanuck.com/tq/ Tips & Tweaks
http://ntcanuck.com/net/board/index.php
news://news.grc.com/grc.techtalk.dns.bind_pe_beta

 

[Ace Fekay [MVP]]

In addition to the other suggestions, have you looked at a possible faulty
cable or connector?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[cepolly]

Just a thought or two:

1) is this machine new to the network?
2) are you running any security software such as black
ice?

the symptoms you describe will also happen if black ice is
installed on the server/machine/router(or router specific
FW protection), if thats your config and you have locked
things down. you would have to explicitly allow the errant
pc to connect to the server/machine/router via a static ip
address. it doesn't sound like this is the issue, but i
thought i'd throw in a different line of reasoning on this.

 

[Michael Johnston [MSFT]]

This could be caused by a few things. The OS itelf is probably not the culprit. Check for any firewall software or other IP filtering. Next most likely culprit is that
the NIC or cable or switch port has gone bad. Try swapping out each of these. Lastly, hard code the NIC speed and duplex settings on the NIC adapter itself.
First use 100 MB full duplex followed by 100MB half and then 10MB half.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.