using 'net use'

[bwanaaa]

everybody stores some data off their local C drive. some of us mount network shares through the 'add a network place wizard, some of us 'map network drives, and some of us write .bat files to invoke 'net use'.

does anyone know the nitty gritty differences between these methods and is willing to share? how is it that the 'add a network place' wizard does not give a share a drive letter? why does it sometimes work, when the other 2 methods do not (net use gives me error 67 on 1 pc but the identical command line - letter for letter - issued on another machine works). How to trouble shoot this issue?

even on the the pc where "net use works" - i have to specify /user:<username> <password> in the command line otherwise that pc also gives error 67. i tried adding a Lmhoststimeout DWORD entry in the registry as some have suggested for 15 secs - no help. if i specify the ip thusly,
net use z: http://iDisk.mac.co/username /user:<username> <password>, i get the error 67 immediately. if i use the unc thusly,
net use z: \\17.250.248.77\username /user:<username> <password>, i get the error 67 after about 10-15 secs. i have read some articles about having a wins entry or an lmhosts entry but do not understand that difference.

The errant pc otherwise surfs the net fine and networks on the lan fine. the target and all the pcs can ping each other. an application, webdrive, has no difficulty mounting the share as a drive letter. can anyone shed light?

 

[Rapidskies]

In a nutshell "net use" & mapping network drives via the GUI are the same. Its like running chkdsk from the command line or right clicking your c: drive and doing error checking. They use the same thing. With that said the "add a network place wizard" is different and has some requirements which I found here http://www.microsoft.com/technet/prodte...xppro/maintain/xpmanaged/34_xpapf.mspx:

"Supporting network places requires the Web Extender Client (WEC) protocol and Microsoft FrontPage® Server Extensions, or the Web Distributed Authoring and Versioning (WebDAV) protocol and Internet Information Services (IIS). The user must also have read and write access to the Web server."

Hope this helps somewhat, take care.

 

[her209]

I've never had any issue with "net use". Are all the PCs in the same domain? Are they in a workgroup? If so, does the connecting computer have a user account with the same password?

 

[bwanaaa]

tnx, rapidskies. it's a beginning.

her209, you've been on here since forever. r ua mod here? the 2 pcs are in a workgroup and the identical usernames and passwords are used on each. the idisk username and pw of course is different.

just for kicks, itried to connect to my idisk from various other pcs at work. interestingly, i found erratic behavior even on the same pc.

using the unc (\\17.250.248.77\user) prompted for username and pw and then did not work with an appropriately long delay. error 67
using the url (http://iDisk.mac.com/user) failed immediately. error 67.
using add a network place presented a credential dialog for usename and pw- it kept rejecting the credentials-but when i canceled out of it ANOTHER 'plainer appearring' credential dialog popped up and IT accepted the same user and pw and then presented myidisk.

from what i've read, the 'webdav redirector service' is flaky.

if you've never had trouble with 'net use' it's probably because you've been connecting to shares from an xp workgroup or xp domain. have you ever tried webdav shares?