Boot delay with Wireless Adapter

[Guest]

I am having a slight delay in boot (after desktop is displayed)

Once my boot completes till desktop.
Yahoo Messenger opened
then
Windows defender also started up
then sound manger icon also comes

but then
it takes a 2-3 minutes for the network adapter icon to appear
(machine isnt slow, processing light doesnt light up in this period)
i cant access network connections during this time
though i can ping to the internet even though the network icon dint appear yet
this is a wireless adapter (static IP)
i tried disabling wireless adapter and starting, stil same
i tried uninstalling it and starting, still same.

any solutions ?

 

[Patrick Keenan]

I am having a slight delay in boot (after desktop is displayed)

Once my boot completes till desktop.
Yahoo Messenger opened
then
Windows defender also started up
then sound manger icon also comes

but then
it takes a 2-3 minutes for the network adapter icon to appear
(machine isnt slow, processing light doesnt light up in this period)
i cant access network connections during this time
though i can ping to the internet even though the network icon dint appear
yet
this is a wireless adapter (static IP)
i tried disabling wireless adapter and starting, stil same
i tried uninstalling it and starting, still same.

any solutions ?

Use Process Explorer to see exactly what is running and what is stalling.

I sometimes find that Windows Update, if set to automatic, will seriously
slow down systems for the first few or many minutes after boot.

HTH
-pk

 

[Esaz]

in message...

[long boot with wireless NIC]

this is a wireless adapter (static IP)

Ok. You already thought of the very first thing everyone else would for the
long boot: DHCP

any solutions ?

First, give your wireless NIC model.

Cisco and DLink, I can likely help. Linksys, less so. Other brands,
others may be helpful.

Until then check your event logs to see if any errors are being generated
and also check that no unneccessary network protocols are being binded to
the [wireless adapter].

 

[Guest]

Even Viewer shows a couple of errors on start. i am pasting them ehre

DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service upnphost with arguments "" in order to run the server:
{204810B9-73B2-11D4-BF42-00B0D0118B56}

The DHCP allocator has disabled itself on IP address 10.12.0.34, since the
IP address is outside the 192.168.0.0/255.255.255.0 scope from which
addresses are being allocated to DHCP clients. To enable the DHCP allocator
on this IP address, please change the scope to include the IP address, or
change the IP address to fall within the scope.

The server could not bind to the transport \Device\NetbiosSmb because
another computer on the network has the same name. The server could not
start.

in message...

[long boot with wireless NIC]

this is a wireless adapter (static IP)

Ok. You already thought of the very first thing everyone else would for the
long boot: DHCP

any solutions ?

First, give your wireless NIC model.

Cisco and DLink, I can likely help. Linksys, less so. Other brands,
others may be helpful.

Until then check your event logs to see if any errors are being generated
and also check that no unneccessary network protocols are being binded to
the [wireless adapter].

 

[Guest]

Wireless CARD MSI International 802.11bg
1033B

in message...

[long boot with wireless NIC]

this is a wireless adapter (static IP)

Ok. You already thought of the very first thing everyone else would for the
long boot: DHCP

any solutions ?

First, give your wireless NIC model.

Cisco and DLink, I can likely help. Linksys, less so. Other brands,
others may be helpful.

Until then check your event logs to see if any errors are being generated
and also check that no unneccessary network protocols are being binded to
the [wireless adapter].

 

[Esaz]

Even Viewer shows a couple of errors on start. i am pasting them ehre

DCOM got error "The service cannot be started, either because it is
disabled
or because it has no enabled devices associated with it. " attempting to
start the service upnphost with arguments "" in order to run the server:
{204810B9-73B2-11D4-BF42-00B0D0118B56}

The DHCP allocator has disabled itself on IP address 10.12.0.34, since the
IP address is outside the 192.168.0.0/255.255.255.0 scope from which
addresses are being allocated to DHCP clients. To enable the DHCP
allocator
on this IP address, please change the scope to include the IP address, or
change the IP address to fall within the scope.

The server could not bind to the transport \Device\NetbiosSmb because
another computer on the network has the same name. The server could not
start.

Ok. Those are a couple hints on why, maybe, the (W)NIC is hanging...

It, of course, could be anything (including even other programs running at
startup), but this looks like it should be tackled first. If not for
anything else, at least to flush it out. (The "hang" may well be because it
thinks there is another computer with the same computer name on a workgroup.
Is there?)

Is this a standalone computer or do you have another computer connected
(ICS'd) to a wire ethernet port on this computer?
(DHCP allocator is used by ICS.)

Where I'm going with this is that I don't know if the IP address issue
should be tackled or not -- since we don't know if this is just a standalone
computer or you have another hanging off it...

 

[Guest]

There are no duplicate ips in network
My networking is absolutely fine
During this stuck boot for a minute or two, i can access net, ping ips etc.
but i cannot open network and dialup connections.

nw event viewer is not logging any errors.

What else can be reason .?