Media disconnected with Static IP address

[Guest]

Hi,

I have two laptops both configured with WIndows 2000 SP4, patched and the
latest network card drivers (both NICs are built-in)
When I assigned a static IP address 10.10.10.1 to one laptop based on the
settings below it works. I can get connected to network\internet.
However on the 2nd laptop it doesn't matter what IP address I use I get
media discconnected message when i do an ipconfig.

I have tried the following:
Inserted a different network card into the laptop, installed updates, got
new NIC drivers. Compared both laptops and as far as I can see they are
configured the same. There is no firewall software on the laptops

The laptop that works is a internal broadcom network card and the one that
doesn't is an internal Intel Pro 10/100.

These settings are specified in a DMZ firewall (sonicwall)
10.10.10.0/24
Usage by Client PC's: 10.10.10.1 - 10.10.10.253
Default Gateway IP: 10.10.10.254


I know that both laptops can get normal netowrk IP addresses (192.168.x.x)
and work fine on the LAN.

Any suggestions please, I am at a loss

Many THanks
Eilish

 

[Phillip Windell]

However on the 2nd laptop it doesn't matter what IP address I use I get
media discconnected message when i do an ipconfig.

It is a "physical" problem.

Bad Nic
Bad cable
Bad port on Switch/Hub at other end of cable
Wrong cable (cross-over vs straight-through)

 

[Guest]

I thought it might be physical however I am using the same cable and port to
connect both laptops (not at the same time).

I tried different NICs in the laptop that wasn't connecting, while I only
mentioned 2 laptops in my discussion I have 2 other laptops in our IT Room
here and they can't connect either. this is why it is baffling - we can't
work out what is special about the laptop that will connect.

So essentially I have a laptop that will connect and since the only thing I
see differently between all of these laptops is the built in NIC. The laptop
that works is a broadcom NIC and the other laptops are a wee bit older and
are using Intel Pro 10/100.

Thanks

 

[Guest]

Also I know that the NIC is working in all laptops as they can connect to the
internal LAN

 

[Frankster]

Some NICs (and switches) have the ability to auto-sense and auto-switch
internally between cross-over and straight through cabling. Others don't.
This feature would obviously have to be supported on both ends.

Could it be that one of your laptops has this ability (along with the
switch) and the others do not?

Try changing the cable to a known good *patch* cable (not a cross-over).

-Frank

 

[Frankster]

Another thought...

Check out the NIC adapter properties... if set to auto-sense media and link
negotiations, try setting to hardcoded (i.e. 100Mb/Full or 10Mb/hale,
whatever). If hardcoded already, set to auto-sense. Try again.

-Frank

 

[Kurt]

So you are saying that changing your IP address from a 192.168.something to
a 10.something generates a media disconnected message? I find that hard to
believe. What else are you changing? Pluging into a router? a different
switch? Something else must be different.

....kurt

 

[Guest]

Hi Frank,

You were right on the money on this one, the broadcom NIC can auto-sense and
is able to connect to the DMZ. The other laptops NIC's can't "switch" so
either of the following solutions work - using a cross over cable or putting
a mini-hub into the configuration. Changing the auto-detect/Full Duplex
settings did not work, NICs too old maybe!

Thanks for your logical and very useful explanation and for not thinking I
was mad, this was a hard one to explain and it was quite easy to blame it on
a "physical hardware problem"

Eilish

 

[Frankster]

Actually, auto-sensing link negotiations is different from auto-sensing
media type (cross-over/non-cross-over). But either one could have caused the
scenario you described.

-Frank