I have experienced this problem 3x already with brand new
computers out of the box, first a Dell then two Sony
Vaios. The problem is as follows; If on your prior use
you NIC card is enabled, and you reboot, as soon as you
login under any user name, it takes like 2 minutes till
you can actually use anything, yet when I disable the
Network Adapter and reboot it boots immediately. I have
tried removing everything out of the startup
in "msconfig" and still no change. I watched the Task
Manager and there is no CPU usage at all and no HD
activity, the computer sits idle till it returns back to
normal on average 1 - 2 min later. Thus I was wondering
if anyone else has heard of this problem before and if
there is a way of resolving it?

If you are NOT connected to a network then the NIC will send out DHCP packets requesting an
IP address. It will contiuously do this until the protocol times out.

What you can do is CHANGE this NIC from DHCP to the following:

IP: 192.168.1.100
MASK: 255.255.255.0

That should stop the NIC from having to use DHCP and cause the pause.

In addition:
If you post to UseNet with your TRUE, not a munged, email address then you have now invited
the Swen worm to visit you.

The Swen is news spelled backwards. The reason it is called this is because the Swen worm
harvests email addresses from UseNet News Groups. It has an engine that allows it to post
itself to UseNet News Groups and well as it has its own email engine. From the list of
email addresses that it has harvested, it will then email itself to those addresses.

Dave L.



"David" <dwener@hotmail.com> wrote in message
news:010401c3d484$844ac4d0$a401280a@phx.gbl...
| I have experienced this problem 3x already with brand new
| computers out of the box, first a Dell then two Sony
| Vaios. The problem is as follows; If on your prior use
| you NIC card is enabled, and you reboot, as soon as you
| login under any user name, it takes like 2 minutes till
| you can actually use anything, yet when I disable the
| Network Adapter and reboot it boots immediately. I have
| tried removing everything out of the startup
| in "msconfig" and still no change. I watched the Task
| Manager and there is no CPU usage at all and no HD
| activity, the computer sits idle till it returns back to
| normal on average 1 - 2 min later. Thus I was wondering
| if anyone else has heard of this problem before and if
| there is a way of resolving it?

I tried just that and the same pause is still occuring
even with a static IP.


>-----Original Message-----
>If you are NOT connected to a network then the NIC will
send out DHCP packets requesting an
>IP address. It will contiuously do this until the
protocol times out.
>
>What you can do is CHANGE this NIC from DHCP to the
following:
>
>IP: 192.168.1.100
>MASK: 255.255.255.0
>
>That should stop the NIC from having to use DHCP and
cause the pause.
>
>In addition:
>If you post to UseNet with your TRUE, not a munged,
email address then you have now invited
>the Swen worm to visit you.
>
>The Swen is news spelled backwards. The reason it is
called this is because the Swen worm
>harvests email addresses from UseNet News Groups. It
has an engine that allows it to post
>itself to UseNet News Groups and well as it has its own
email engine. From the list of
>email addresses that it has harvested, it will then
email itself to those addresses.
>
>Dave L.
>
>
>
>"David" <dwener@hotmail.com> wrote in message
>news:010401c3d484$844ac4d0$a401280a@phx.gbl...
>| I have experienced this problem 3x already with brand
new
>| computers out of the box, first a Dell then two Sony
>| Vaios. The problem is as follows; If on your prior use
>| you NIC card is enabled, and you reboot, as soon as you
>| login under any user name, it takes like 2 minutes till
>| you can actually use anything, yet when I disable the
>| Network Adapter and reboot it boots immediately. I
have
>| tried removing everything out of the startup
>| in "msconfig" and still no change. I watched the Task
>| Manager and there is no CPU usage at all and no HD
>| activity, the computer sits idle till it returns back
to
>| normal on average 1 - 2 min later. Thus I was wondering
>| if anyone else has heard of this problem before and if
>| there is a way of resolving it?
>
>
>.
>