Re: Log DHCP request with Sniffer/Ethreal...
From: Malic (spam_at_houston.rr.spam)
Date: 09/01/04
- Next message: Ulf B. Simon-Weidner [MVP]: "Re: DNS help"
- Previous message: Matt: "moving the system root from one partition to another."
- In reply to: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Next in thread: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Reply: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 1 Sep 2004 14:12:39 -0500
WSe have spanning tree turned off. We are running older Baystack 303 10/100
switches and the NIC onboard is 10/100/1000. Our theory is that the driver
is bad and doesns't detect network speed until late in the login. It is
then too late to run login script and the users are logging into the lacally
cached windows xp account.
The onboard nic is intel 10/100/1000 VM
"Roger Hunen" <rhunen@xs4all.nl> wrote in message
news:Osy61A%23jEHA.632@TK2MSFTNGP12.phx.gbl...
> "Malic" <spam@houston.rr.spam> wrote...
>> We are experiencing the following issue with new PCs we have purchased
>> from
>> IBM. We did not experience the issue with machines before the IBM
>> thinkcentres we purchased.
>
> You may be looking in the wrong place. This may not be IBM thinkcentre
> related
> at all. You may be experiencing this problem simply because you have
> faster
> machines now. Read on...
>
> [snip]
>
>> Issue:
>> On a warm or cold boot, immediately login and it will not run our kixtart
>> login script form Domain. After being logged in for 30 seconds to 1
>> minute
>> we then get our network connection. Browse internet connec tto email
>> etc...
>> We have to log off and log back in to reprocess our login script.
>
> This sounds _very_ familiar to me...
>
> Assuming that you have a switched network, make sure that workstation
> ports
> go into the forwarding state as soon as link integrity is established. On
> Cisco
> switches the feature you are looking for is called 'portfast'.
>
> Normal spanning tree behavior is to set a port blocking until the spanning
> tree
> protocol has decided that it must be forwarding. This takes 30-40 seconds.
> During this time the port blocks all traffic. So DHCP will fail and you
> cannot
> talk to your domain controllers.
>
> For old slow systems, this may not be a problem because the system boot
> takes longer than it takes spanning tree to set the switch port
> forwarding.
> New fast machines will complete the boot cycle before the port goes into
> the
> forwarding state and have no network connection for some time.
>
> When configuring portfast, the port goes into the forwarding state
> immediately
> and the spanning tree protocol may switch is back to blocking if there is
> a good
> reason to (no workstation attached but another network switch that is
> closer to
> the spanning tree root).
>
> Alternatively you can swith off spanning tree at workstation ports, but
> portfast
> is much more fool proof.
>
> Good luck,
> -Roger
> --
> E-mail: rhunen@xs4all.nl
> Home: http://www.xs4all.nl/~rhunen
>
>
- Next message: Ulf B. Simon-Weidner [MVP]: "Re: DNS help"
- Previous message: Matt: "moving the system root from one partition to another."
- In reply to: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Next in thread: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Reply: Roger Hunen: "Re: Log DHCP request with Sniffer/Ethreal..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
