trouble getting pc on network

[kanin247]

To Whom It May Concern:

I am trying to get my computers (PC1, PC2, LAPTOP1) onto my network and I was successful on TWO of THREE. I have an Efficient Networks 4-Port DSL/Cable Router (2614) where each computer on the network should get a 192.168.254.xxx IP address. PC1 and LAPTOP1 get a valid IP address by simply connecting the Ethernet cables (which is how it should be). However PC2 receives a different one (169.254.132.94) when I connect the cable. I made sure all the auto detect stuff is NOT checked and made sure the driver for the network card works but still no luck in recognizing. What could be causing this and how do I go about resolving this issue?

I appreciate your help. Thanks!

kanin247

 

[manarth]

An IP of 169.x.x.x means that the client cannot connect to the DHCP server to get an address.

- check the network cables, check for link lights (on both the client and the router) when you plug the cable in

- make sure there is enough IP address available in the DHCP pool

- if no joy, try reinstalling (the latest) network drivers

- if still no joy, try the now-famous winsock repair tool:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[bcastner]

In addition to Manarth's list:

1. Make sure your TCP/IP properties are set to obtain an IP address automaticly;

2. Make certain there are no firewall issues;

3. Add odd problem I have seen, if you uninstalled Norton Anti-virus: &quot;DHCP errors after uninstalling Norton Antivirus&quot;

http://www.bl.com/moshe/text/quiddities/norton_errors.html

 

[kanin247]

manarth,

ok, i'll check the drivers and see if its the most recent. and also look at that winsockfix file. i'll keep the post updated, stay tuned...

on a side note, PC1 & LAPTOP1 are running Win2K (the ones that connect fine) and PC2 is running WinXP (the one that is NOT connecting fine). i thought xp was suppose to solve everything...haha. oh well...

thanks for your help!

kanin

 

[MountainNetworks]

I'm having almost the same problem.

We have several machines on our network. All running either win2k or XP Pro. The machine with the problem is running XP Home.

Dell Dimension 2100 originally came without a network card. I added a Belking network card and plugged it into the net. No luck. I returned the Belkin network card and got a new netgear FA311. Still no luck. Took the machine down to a desk where I know the connection was good. Still nothing. Took the card out and put it in a different machine. Works great, so it's not the card.

I can ping all IP addresses in the 192.168.xx.xx network, but I can't ping anything outside by name or by IP address. When I first started this charade, there was this WAN Adapter thing in the device manager. I removed it. still no luck. so I readded it (the adapter is made by AOL) and tried to make a bridge. Still no luck. Deleted the bridge and the WAN Adapter from AOL. Same behavior.

I'm at my wits end with this machine. Why is this the only machine on the network that can't ping anything on the outside. It feels like an XP Home issue, but I can't be sure. Let's recap...

Cable Ok.
Network Card Ok.
All Other machines Ok.
This is the only machine on network with XP Home...everyone else is XP Pro or Win2k Pro.

Connection is DSL which goes into a firewall, which goes into a hub which connects all the machines. Everyone can access internet except this XP Home machine.

I'm ready to throw this machine against the wall into a million pieces Help??!

Thanks....

 

[manarth]

MountainNetworks - sounds like a configuration issue...
get the full info by going to a command prompt (run &quot;cmd.exe&quot and entering the command &quot;ipconfig /all&quot;.

if you copy and paste the information here, it may give us an indication of the problem.

as you can ping stuff on the 192. subnet, we can rule out cable failure! try the command &quot;tracert google.com&quot; to see where the connection fails.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[bcastner]

Disable the XP ICF native firewall.
It is located on the network connection property tab, Advanced.

 

[MountainNetworks]

Hi:

Been there, done that ipconfig /all says the same thing as all the other machines on the network...except the last octet of the primary IP of course. ICF is disabled.

Basically the problem is that the tcp/ip isn't binding to the network adapter, in spite of my specifically telling it to do so. At least that's what it seems like. Except for the fact that the machine can't ping any IP's outside the network. Then again, if it was a binding issue, I wouldn't be able to ping anything at all. All that money I spent on getting my MCSE didn't prepare me for this

Thanks...

 

[bcastner]

Time maybe to fix your winsock service stacks:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

 

[manarth]

if you can ping the subnet, and can ping the gateway, i'd suggest having a look at the firewall logs to see if they give any indication of what the problem is.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[kanin247]

update...

installed new drivers - still no connection.
ran winsockfix - still no connection.

however, i did notice that only 1 of 3 leds on the NIC card (3Com EtherLink XL 3C905B-TX) were on (ooo = 10LNK 100LNK ACT). so, the leds are telling me there's no connection to the network, which i knew since the ip address (169.x.x.x) is wrong. i know the cable/port on router is good b/c i tried it on PC1 and LAPTOP1 and it connected fine. what else could be causing the connection to fail?

i appreciate your help, thanks!

kanin

 

[manarth]

no link lights (normally) = bad cable / bad NIC.
try a different network card.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[kanin247]

well, the i know the cable is good b/c i checked it with my other PCs and it worked fine. but the NIC does light one led (10LNK), so doesn't that mean that it's not entirely dead?

kanin

 

[bcastner]

This sounds like an autonegotiation failure. If you are connectecting to a switch, set the adapters Advanced setting to force 100 mbs with Full Duplex.

If there are no other issues, you should see additional lights come on for the adapter.

 

[kanin247]

ok, i'm not getting anywhere. so, i'm gonna solve this problem the easy way - fork out $10 and purchase a new NIC card.

thanks to everyone who provided some assistance!

kanin