Ctrl-Alt-Del

Thank You, Thank You, Thank You!!! That worked! I struggled with the NET USE command for a bit tonight though because I did not realize that there was supposed to be a space in the syntax between the drive letter and the machine name section. To clarify the use of this gem for some people, I am going to write the correct use of the command with underscores in the syntax. Take out the underscores and replace them with spaces and you will be all set. Include the quotes too! The quotes are not always necessary but it would be a safe bet for a beginner to just get in the habit of using the quotes. Even if you use the quotes when you don't need to, the command will still work, but if you fail to use them where you should, then the command will fail (the quotes help parse and pass long names that have spaces in them through the command). Example: net_use_x:_"\\machinename\sharename" Now that the workaround is in the open, can anyone shed some light on why Windows XP SP2 won't authenticate users who try to access shares on an XP SP2 system by using the ERD Commander 2005 GUI? But yet this tiny little prog...NET USE, can get the job done? This is not a really important question at this point, but if anyone wants to share...please do.

Hello, we have been using ERD Commander for a while now from one of our multi-boot CD's to perform unattended XP installs that get pulled down from a network share on our LAN. Our network is a LAN and nothing more; we do not have a server, so there is no domain. This has worked for a long time; we have always been able to map a drive letter from within ERD commander to a separate Windows XP machine that we use specifically as a storage point for our HD images and installation programs. After we updated this separate storage point to XP SP2, we lost the ability to map network drives to any of the shares on the storage point from within ERD commander. We CAN do file sharing just fine with no problems and map drives to the XP SP2 machine when we use **real installations of windows; the functionality only seems to be messed up when we try to access the shares on our XP SP2 storage point from computers that we have booted by using ERD Commander. Our ERD commander sessions can access shares on Windows 2000 and Windows XP SP1 machines, but for some reason it can not access shares on any machine that has Windows XP SP2 running on it. When we try to access shares on an XP SP2 machine from another computer that is running an ERD Commander session, ERD Commander kicks out a "Network Error 5", accompanied by a message that says "Access is denied". The weird thing is that we can go to the machine that ERD commander can not access, and we can then use that machine to access the shares that are available on the computer that was booted with ERD commander. So the problem has a one way aspect. I did run a ping test from within ERD Commander to the IP of the XP SP2 machine; the ping was fine. On the SP2 machine we are positive that file and print sharing is set up correctly, and we have turned off the Windows firewall for testing purposes, but ERD still can not gain access to the shares on the XP SP2 machine. Again everything works fine when we try to get our computers to talk to each other using **real windows installations. What do you think is the problem? Is it an ERD Commander problem, or is their something unique to LAN networking that changed in XP SP2 that does not recognize incoming authentication requests from an ERD Commander session? I have cruised through TCP/IP settings, NetBIOS over TCP/IP, Group Policy Settings, Local Users and Groups; I just don’t know how to get it to work. I guess the simple solution is to make sure that the storage point is using XP SP1 or Windows 2000, but this weird problem has been grating on me for a few days now. I know that many of you have experience with ERD Commander and so I thought maybe one or more of you may have stumbled upon this problem...