right ... so i have this vista (ultimate) computer (don't laugh, guys :) i mapped 2 network drives (reconnect at next logon). now when i start the computer the 2 drives show a red X on the icon. this is because Vista is initializing the drives (telling me 192.168.xxx.xxx is not accessible) BEFORE the network connection is fully up and running (i have tried both static IP and DHCP). i can open the drives once the LAN connection is established and the problem is solved ... but still annoying. Windows Firewall is running with the default settings. any suggestions?

Might use a script running a net command. Might have to put some waits in if the network takes a long time. Map should work you'd think. Those wacky guys in Redmond. I read it wrong and answer it wrong too. So get off my case you peanut.

elsewhere i hear this is 'normal behaviour' ... normal my blue eyes :)

Be sure the 'host' is up and running and logged in before you attempt to access the shared mapped drives. Additionally, if you have added accounts which now require you to log on in some way instead of jumping to the desktop you have now invoked what I call increased security measures and your shares/permissions need to be established for the user(s) on the resources in question. There's another consideration too - by default since service pack 2 , XP now will autodissconnect any mapped drives that havent been accessed in 15 minutes (or so ) to free up network resources...lol ... that would have been helpful in the days of netbeui and such but TCP is the protocol of choice now so its totallly crap... i have a script that I wrote that runs as a batch file at start up to delay autodisconnect to 7800 years ... should be long enough to get my stuff done. The script to use to set your machine to not autodisconnect is to make a text file in notepad and save as a batch file: net config server /autodisconnect:-1 If you dont know what a batch file is,,,well,,you better learn that too. To function, once the file is made I placed it in the startup group folder as startingup.bat and youll see it execute at boot up. I run it every day. Do not disable your firewall on your server you may be disabling your network abilities believe it or not as MSFT has integrated the network services with the firewall. The firewall will not prevent solicited traffic between 2 workstations in general. that should help but be sure to add the proper users and passwords to each and every machine involved otherwise it may only work occasionally if at all. OH and allow for the proper control in the security settings on the share/mapped drive otherwise you may be limited to read only. Workgroups must have matching users on each and EVERY machine if resouces are to be shared properly... I know a way around this but thats another topic. Did I post this to the right question ... i hope so my fingers are sore. Theres more to the system than you might think...