Long delay on "Connect to a network" after upgrading to Vista

This seems to be a common problem, to which I have not found a fix.
Long delay after clicking Connect to a Network in the system tray. Up to 30
seconds.
Do Microsoft acknowledge the problem? Any plans for a fix?

I have about 15 VPN connections on my laptop. With XP I would go Start ->
Connect to -> Customer, job done. I could then right-click and select status
from the system tray and see my IP address and the subnet of the destination
network.

With Vista, not only do I have this long delay, but the whole process is so
convoluted. When the Connect to a Network dialog box eventually opens, I
have a daft small box that I have to scroll through to find the network I
want to connect to. Then finding the subnet requires more messing about.

Is there an easier way? A shortcut to Network Connections on my start menu
seems to be about the best so far. It was better with XP.

I didn't want to upgrade to Vista, but it's awkward when customers call up
and they've gone out and bought a new machine with Vista on it, and I don't
know my way around yet. Ho hum

File and Printer Sharing in Windows Vista
http://technet.microsoft.com/en-us/l.../bb727037.aspx

Windows Vista Support WebCast: Troubleshooting Network Issues on Windows Vista - New Network Diagnostics
http://support.microsoft.com/kb/927551

Network Diagnostics Technologies in Windows Vista
http://www.microsoft.com/downloads/d...displaylang=en

--
Carey Frisch
Microsoft MVP
Windows Shell/User

---------------------------------------------------------------

"Carl Farrington" <> wrote in message news:...
This seems to be a common problem, to which I have not found a fix.
Long delay after clicking Connect to a Network in the system tray. Up to 30
seconds.
Do Microsoft acknowledge the problem? Any plans for a fix?

I have about 15 VPN connections on my laptop. With XP I would go Start ->
Connect to -> Customer, job done. I could then right-click and select status
from the system tray and see my IP address and the subnet of the destination
network.

With Vista, not only do I have this long delay, but the whole process is so
convoluted. When the Connect to a Network dialog box eventually opens, I
have a daft small box that I have to scroll through to find the network I
want to connect to. Then finding the subnet requires more messing about.

Is there an easier way? A shortcut to Network Connections on my start menu
seems to be about the best so far. It was better with XP.

I didn't want to upgrade to Vista, but it's awkward when customers call up
and they've gone out and bought a new machine with Vista on it, and I don't
know my way around yet. Ho hum

"Carey Frisch [MVP]" <> wrote in message
news:C7CBE51B-BDA4-4231-8CB2-...
> File and Printer Sharing in Windows Vista
> http://technet.microsoft.com/en-us/l.../bb727037.aspx

The above seems totally irrelevant. It discusses how to setup peer to peer
smb/cifs sharing in a non domain environment. How does that relate to what
/looks like/ a bug in Windows Vista? My laptop is part of my active
directory 2003 domain BTW, not that I would think it relevant to the
problem.


>
> Windows Vista Support WebCast: Troubleshooting Network Issues on Windows
> Vista - New Network Diagnostics
> http://support.microsoft.com/kb/927551
>
> Network Diagnostics Technologies in Windows Vista
> http://www.microsoft.com/downloads/d...displaylang=en

These will be worth a read - thanks, due to my current unfamiliarity with
Vista in general and its new tools and ways of doing things. I still suspect
my problem to be a bug however, but perhaps the diagnostic tools will point
towards something. Maybe Vista is trying to contact my DC.. ? (I'm working
remotely, permanently, for the time being.. perhaps the active directory
environment is relevant after all).

As with others who have this problem, a shortcut to Network Connections
works perfectly, but right-clicking the Network icon in the system-tray and
selecting "Connect to a Network" results in a 30 - 60 second delay before
anything happens. Nothing noted in the event logs.

cheers,
Carl