Re: How to reconnect an ethernet connection
From: Grant Edwards (grante_at_visi.com)
Date: 04/28/05
- Next message: Jean-David Beyer: "Re: updating redhat systems in a secure environment?"
- Previous message: Mark Parker: "updating redhat systems in a secure environment?"
- In reply to: Tristan Miller: "Re: How to reconnect an ethernet connection"
- Next in thread: Vladimir Florinski: "Re: How to reconnect an ethernet connection"
- Reply: Vladimir Florinski: "Re: How to reconnect an ethernet connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 28 Apr 2005 21:22:25 -0000
On 2005-04-28, Tristan Miller <psychonaut@nothingisreal.com> wrote:
>> What do you mean by "doesn't reconnect to the network"? The
>> link active status never comes back on?
>
> What status? You mean the LED on the router?
The LED on the PC's NIC or the link status returned by the
Ethernet driver (up/down, 10/100, half/full). There's a
utility you can use to look at the link status (not all drivers
return link status, but most do). I can't remember the name of
it. I doubt that the link layer is the problem if the same
move works for Windows machines.
> Can't ping anything, including local machines.
>
>> Are the two ports on the same subnet?
>
> No idea.
Are you using static IP addresses or DHCP?
If you're using DHCP, it could be that the two ports are on
different subnets. If moving Windows machines between the two
locations does work, look to see what the PC's IP address and
netmask is before and after the move.
If you're moving between subnets, then you've got to tell the
dhcp client to request a new address when you get to the new
port. It could be that Windows does this automatically when
the link status goes down/up. I don't think most Linux setups
do.
>> Does it work if you just wait a while (5-10 minutes)?
>
> That's one thing I haven't tried -- in my experience with MS-Windows
> machines on the same network, the connection reestablishes in under a
> minute. I'm on vacation now, but when I get back, next time I'll try
> waiting a few minutes. Though I still think it's a problem with my
> client, not the network, given that Windows machines have no problems
> whereas my SuSE system does.
My first guess: you're using DHCP, and the two ports are on
different subnets and therefore require different IP addresses
and/or subnet masks. Windows must be requesting a new address
via DHCP when it detects the link status change, and Linux must
not be. I don't know if there's a way to configure Linux to
request a new DHCP lease when the link status goes down and
then up.
Again, this is just a semi-educated guess.
If you're using static IP addresses, and it works for Windows
and not for Linux, then I'm stumped.
--
Grant Edwards grante Yow! Did I say I was a
at sardine? Or a bus???
visi.com
- Next message: Jean-David Beyer: "Re: updating redhat systems in a secure environment?"
- Previous message: Mark Parker: "updating redhat systems in a secure environment?"
- In reply to: Tristan Miller: "Re: How to reconnect an ethernet connection"
- Next in thread: Vladimir Florinski: "Re: How to reconnect an ethernet connection"
- Reply: Vladimir Florinski: "Re: How to reconnect an ethernet connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
