ipconfig - Media Disconnected

[Man Utd]

I have 2 PC XP connecting to Netgear Modem Router DG834.
I turned on my 1st XP SP3 and did not connect to internet, typep ipconfig
showed
"Media disconnected"
Device manager showed the network adaptor work properly.

I then turned on my 2nd PC, that can connect internet with no problem.

Both pc are set Obtain IP address dynamically.

I thought my 1st PC network adaptor problem but it is not because when I set
its IP address the same as 2nd pc, the 2nd pc screen showed there is IP
conflict on my 1st pc. So the network is not a problem.

I searched Google it looks like there is solution to uninstall driver,
re-install driver, restore XP, ...etc.
But it looks like no definite source of problem.

I have been using these 2 pc for over 2 years. The problem only arise
yesterday in my 1st pc.


I also tried the Windows 7 beta on my 1st pc with IE, it detected a problem
and tried to fix, prompted there is no valid IP configuration.

Any idea?

 

[Guest]

I have 2 PC XP connecting to Netgear Modem Router DG834.
I turned on my 1st XP SP3 and did not connect to internet, typep ipconfig
showed
"Media disconnected"
Device manager showed the network adaptor work properly.

I then turned on my 2nd PC, that can connect internet with no problem.

Both pc are set Obtain IP address dynamically.

I thought my 1st PC network adaptor problem but it is not because when I set
its IP address the same as 2nd pc, the 2nd pc screen showed there is IP
conflict on my 1st pc. So the network is not a problem.

I searched Google it looks like there is solution to uninstall driver,
re-install driver, restore XP, ...etc.
But it looks like no definite source of problem.

I have been using these 2 pc for over 2 years. The problem only arise
yesterday in my 1st pc.

I also tried the Windows 7 beta on my 1st pc with IE, it detected a problem
and tried to fix, prompted there is no valid IP configuration.

Any idea?

what is your Ip configuration?

Media disconnected may mean your cable is stuffed, try use the working
one on the pc that doesnt work. I would also suggest trying an x-over
cable instead of a straight through (or vice-versa) but if you say it
was working before then that is unlikely to be the issue.

Just go through one by one and check each component, use a working
cable, connect pc1 to the netgear port that you know is working, use
the IP settings off the working pc on the not working pc, if you can,
try the working NIC in the not working pc.. etc etc until you find
where the problem lies.

Flamer.

 

[Man Utd]

what is your Ip configuration?

Media disconnected may mean your cable is stuffed, try use the working
one on the pc that doesnt work. I would also suggest trying an x-over
cable instead of a straight through (or vice-versa) but if you say it
was working before then that is unlikely to be the issue.

Just go through one by one and check each component, use a working
cable, connect pc1 to the netgear port that you know is working, use
the IP settings off the working pc on the not working pc, if you can,
try the working NIC in the not working pc.. etc etc until you find
where the problem lies.
*************************************************************8
Hi,

Thanks for your advices.
I noticed the light on Modem Router is 'On' for my both pc, so the network
cable should be fine. Right?
And as I tested set the 1st pc the same IP address as my 2nd pc, the 2nd pc
detected IP conflict, that's to say the network cable working fine?

In addition, in my 1st pc, I tired both original XP SP3 and Windows 7 beta
also internet cannect be connected, that means the NIC is the problem?

 

[Man Utd]

what is your Ip configuration?

Media disconnected may mean your cable is stuffed, try use the working
one on the pc that doesnt work. I would also suggest trying an x-over
cable instead of a straight through (or vice-versa) but if you say it
was working before then that is unlikely to be the issue.

Just go through one by one and check each component, use a working
cable, connect pc1 to the netgear port that you know is working, use
the IP settings off the working pc on the not working pc, if you can,
try the working NIC in the not working pc.. etc etc until you find
where the problem lies.
*************************************************************8
Hi,

Thanks for your advices.
I noticed the light on Modem Router is 'On' for my both pc, so the network
cable should be fine. Right?
And as I tested set the 1st pc the same IP address as my 2nd pc, the 2nd pc
detected IP conflict, that's to say the network cable working fine?

In addition, in my 1st pc, I tired both original XP SP3 and Windows 7 beta
also internet cannect be connected, that means the NIC is the problem?

Hi, this is my IP Config:

Windows IP Configuration
Ethernet Adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address: 169.254.209.45
Subnet Mask: 255.255.0.0
Default Gaetway: 169.254.209.45

 

[John Wunderlich]

Hi, this is my IP Config:

Windows IP Configuration
Ethernet Adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address: 169.254.209.45
Subnet Mask: 255.255.0.0
Default Gaetway: 169.254.209.45

One thing that is apparent is that it is not properly negotiating for a
DHCP address. When you set the IP address manually, you get a conflict
message on the other computer. To me, this indicates that of the four
active wires in a 10/100-Base-T connection, likely one of the outgoing
wires may not be functional. Assuming you've tried swapping cables,
this leaves a bad NIC as the most likely candidate.

However, it is also possible that the NIC is not correctly sensing
and/or setting the Speed/Duplex of the connection. Go into the
advanced settings of the NIC and take the Speed/Duplex settings off of
"Auto" and force it to the correct setting for your router. (For
connecting to most home routers, this would be either 10/Full or
100/Full).
Start->Run->devmgmt.msc
then double-click on NIC card and select the "Advanced" tab.

HTH,
John

 

[Man Utd]

One thing that is apparent is that it is not properly negotiating for a

DHCP address. When you set the IP address manually, you get a conflict
message on the other computer. To me, this indicates that of the four
active wires in a 10/100-Base-T connection, likely one of the outgoing
wires may not be functional. Assuming you've tried swapping cables,
this leaves a bad NIC as the most likely candidate.

However, it is also possible that the NIC is not correctly sensing
and/or setting the Speed/Duplex of the connection. Go into the
advanced settings of the NIC and take the Speed/Duplex settings off of
"Auto" and force it to the correct setting for your router. (For
connecting to most home routers, this would be either 10/Full or
100/Full).
Start->Run->devmgmt.msc
then double-click on NIC card and select the "Advanced" tab.

I just don't understand if the NIC is dead, why when I set my first pc the
same IP as the 2nd one it showed on the 2nd pc screen there was IP conflict?
If the NIC of my 1st pc is dead then the 1st pc should not be 'able' to
connect to the modem/router, its IP should not be 'known' by the 2nd pc,
right?

In addition, can I assign any IP to my pc?

eg.
192.168.0.11
192.168.0.19
192.168.0.22
192.168.0.121
?

 

[John Wunderlich]

I just don't understand if the NIC is dead, why when I set my
first pc the same IP as the 2nd one it showed on the 2nd pc screen
there was IP conflict? If the NIC of my 1st pc is dead then the
1st pc should not be 'able' to connect to the modem/router, its IP
should not be 'known' by the 2nd pc, right?

In addition, can I assign any IP to my pc?

eg.
192.168.0.11
192.168.0.19
192.168.0.22
192.168.0.121

There is a lot of negotiation involved in obtaining an IP address using
DHCP. All that is eliminated if you assign it a fixed address. Of the
four wires used in a 10/100-base-T ethernet connection, two are input
and two are output. Assume that one of the output wires is not
connected. Then an IP packet sent to discover an IP conflict will be
properly received by the board. The response it generates may not be
perfect, but might be enough to make it known to the rest of the
network that it responds to that address -- and it generates that
conflict.

You can use any 192.168.0.x address that is not used, but it is
advisable to stay out of the range of addresses that are assigned by
the router's DHCP server.

HTH,
John

 

[Man T]

HI,

I just disable my onboard LAN and bought a NIC, it nows working perfectly.

My ipconfig:
IP Address: 192.168.0.2
Subnet Mask: 255.255.255.0
Default Gaetway: 192.168.0.1