Here Try this. This is the code to add the network Drive Dim WshNetwork as Object WshNetwork = CreateObject("WScript.Network") WshNetwork.MapNetworkDrive("L:", "\\Server\Resource") Of course you can have the letter be whatever and just fill in your resource Here is the Code to remove it after the object is created WshNetwork.RemoveNetworkDrive("L:") And of course it the letter that you specified earlier. I hope this helps

I think the key is to enumerate the Properties collection of each child node in the collection of DirectoryEntry children. While there may be a more elegant way of doing so, the way that I was able to get a list of users, for example, was to do something like this: Dim entry As New DirectoryServices.DirectoryEntry For Each child As DirectoryServices.DirectoryEntry In entry.Children Dim propertyValue As Integer = 0 Try propertyValue = CType(child.Properties("UserFlags").Value, Integer) Catch ex As Exception ' if it throws an exception, it's not a user item propertyValue = 0 End Try If (propertyValue = 513) Then Console.WriteLine(child.Name) End If Next If you look at the property names in the Properties collection, you should be able to isolate which ones are Domains, which ones are workgroups and which ones are users, etc. I believe there may be a more elegant solution, but I haven't found the best reference for that solution yet. What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.

If everything is in the same workgroup or domain (and the Administrator account presumably has permission to everything in the workgroup or domain) then you may simply refer to the location using the UNC path -- i.e., "\\machinename\sharename\foldername\", and you will not have to expend any additional effort with coding for file access & security permissions.

How about using P/Invoke to call WNetAddConnection2?

You can get the list of machines that are both in the Directory and logged into Active Directory using the methods described here[^]. There is an introduction to using the Active Directory objects in VB here[^]. RageInTheMachine9532

Then you really can't do that. You would have to write an app that can capture all the packets that come by the machine it is running on. This would only work on Ethernet segments that are running on hubs. Switches will prevent you from seeing all the packets, which is what most corporate networks are going to be built with. RageInTheMachine9532