LAN Connection not created unless reboot with cable plugged

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I wonder if anyone else has run into this problem and have an answer!

The setup:
Dell Inspiron 8200 notebook,
Windows Server 2003 (set up for local Workgroup),
DI-624 router.

The situation:
The network connection is set up for automatic IP assignment. The machine is
connected to the router from where it retrieves an IP.

If I reboot my machine with the LAN cable unplugged (say, I'm too far from
the router, or using wireless connection), and then as needed, I try to plug
in the cable to get a connection, the traffic doesn't even start (in the
connection properties, I've made sure that the "power-saver" option is
cleared so the port should have power all the time). Besides, in cases when I
do get the connection, if I unplug the cable and then after a few seconds,
plug it back in, the connection revival takes a long time.

The only way to get the traffic going and to get the IP is to reboot the
machine with the cable already plugged in. Interestingly, the wireless ports
work as expected. I can plug in a wireless adapter card anytime and it
immediately gets the IP from the same router without any problem and I can
use all the local networking and/or internet without any problem.
Unbelievable! Can anyone help solve this mystery?

TIA.
 
Max said:
Hi,
I wonder if anyone else has run into this problem and have an answer!

The setup:
Dell Inspiron 8200 notebook,
Windows Server 2003 (set up for local Workgroup),
DI-624 router.

The situation:
The network connection is set up for automatic IP assignment. The machine is
connected to the router from where it retrieves an IP.

If I reboot my machine with the LAN cable unplugged (say, I'm too far from
the router, or using wireless connection), and then as needed, I try to plug
in the cable to get a connection, the traffic doesn't even start (in the
connection properties, I've made sure that the "power-saver" option is
cleared so the port should have power all the time). Besides, in cases when I
do get the connection, if I unplug the cable and then after a few seconds,
plug it back in, the connection revival takes a long time.

The only way to get the traffic going and to get the IP is to reboot the
machine with the cable already plugged in. Interestingly, the wireless ports
work as expected. I can plug in a wireless adapter card anytime and it
immediately gets the IP from the same router without any problem and I can
use all the local networking and/or internet without any problem.
Unbelievable! Can anyone help solve this mystery?

TIA.
Click to expand...

Instead of rebooting, try disabling and then enabling the LAN
connection.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Yes, it worked; should have thought about that <g>, sorry. Would you mind
explaining the phenomenon a little, to understand the real cause of this
problem.

Also, I will research a way to disable-enable-cycle by using a batch file.

Thanks.
 
Max said:
Yes, it worked; should have thought about that <g>, sorry. Would you
mind explaining the phenomenon a little, to understand the real cause
of this problem.

Also, I will research a way to disable-enable-cycle by using a batch
file.

Thanks.
Click to expand...

Could be any of several things. Some laptops disable devices that are not
being used to conserve power. This can mix Windows up. Some NIC chipset
drivers don't work properly if there isn't a connection when Windows starts
up. Probably more reasons as well.

Kerry
 
Thanks for the reply. I'm sure it's neither one of the two reasons you
mentioned. The connection has been explicitly cleared from power-save option,
and the same NIC chipset used to work with Windows XP before I loaded 2003.
So, it must be some other reason. Thanks for taking a shot though, it helps
finding the reason by elimination.
 
Kerry, thanks for the followup. I just downloaded the nic driver and
installed the driver followed by the usual reboot. Checked the driver version
(4.26) and confirmed the provider to be 3Com. Sadly, the problem still
persists. Strangely, now I don't have the power-saver option available for
the user to decide on it anymore. Oh well ... this was just some feedback on
your suggestion. Thanks again.
 
Let us know if you find the solution.

Kerry
Kerry, thanks for the followup. I just downloaded the nic driver and
installed the driver followed by the usual reboot. Checked the driver
version (4.26) and confirmed the provider to be 3Com. Sadly, the
problem still persists. Strangely, now I don't have the power-saver
option available for the user to decide on it anymore. Oh well ...
this was just some feedback on your suggestion. Thanks again.
Click to expand...
 
Back
Top