>>>>>>We have a client who has a peer to peer network using W2K Professional. Can I expect my apps (7.0) to work just like they do on W2K Server based network? What problems or challenges might I encounter?
>>>>>
>>>>>Yes in general, but no, in a number of ways that will affect the administration of the network. While shared resources are addressed using UNCs and mapping, you'll have to create accounts for each user on each machine, since no authentication services are really available. You also have some interesting issues regarding the allocation of shared resources; you are inherently limited to a total of 10 sessions of simultaneous access to any given system - this means that if you have two shares on a machine that are needed, one a printer and the other a folder, you're not going to be happy when user #6 tries to go in, and it can be rather obnoxious about refusing to drop what might otherwise be considered a dead session pending an explicit logout. You have relatively limited control over how the OS allocates its resources; you're basically limited to favoring the foreground process.
>>>>
>>>>Ed, when you say 10 sessions do you mean 10 log ons to the shared machine. Nobody uses the shared machine as a work station but this still makes me nervous.
>>>
>>>No, a connection to a share is a session; you may log in once, but if you use a shared printer and a shared folder, that's two sessions. And once a session is established, you need to explicitly release the session - if you access a shared folder, that establishes the session, but the session remains intact until the client system explicitly releases the shared resource, even if no files on the share are open, until that share is disconnected, the session remains...
>>
>>Ed, how can a client explicitly release a session? TIA
>
>Well, one way is to explicitly release the shared resource using the API call WNetCancelConnection2() (you can probably get away with calling WNetCancelConnection(), but it's a legacy call that's going to stop working at some point. Resources mapped with the WScript.Network object are explicitly released using the RemoveMappedDrive() and RemovePrinterConnection() methods -if- they are explicitly mapped, but if they are inheritance mapped and accidentally referenced by their UNC rather than explicitly mapped using WScript.Network to actual devices, you may create sessions without actually being aware that they've been created...

Ed, thanks for your help. I will get this resolved with the client.