<div>
 
Hey, 
 
How are you mapping the drive in the script? Which command are you using? 
 
Chris
</div>

<div>
one is with the net use command: net use P: \\server\share and the other is by a .vbs script i got off the internet. i just added my server and share to it...they work fine on local subnet of the domain..but will not show up at remote sites on different subnet...the computer is joined to the domain.. 
 
.one thing i did find out yesterday is that i am able to ping server from remote site, but from the server i cannot ping the client machine on the remote site by name or ip address...when i am at the remote site nslookup resolves back to 1st dns server and if i put the 2nd dns servers name or ip address in it resolves...so that i would assume is telling me that dns is working the way it should....thanks for any help...
</div>

<div>
 
You can map them after logon has completed? 
 
The Windows Firewall does have a default rule that only allows file sharing within the local subnet. However, if you can map after the event it's unlikely that's the cause. 
 
We probably do want to do a bit more work on capturing any potential errors while the scripts are running. 
 
For &quot;net use&quot; we can potentially just redirect output to a text file. 
 
e.g. 
 
net use g: \\server\share &gt;&nbsp;%Temp%\NetUse.log 
 
For VbScript we'd &nbsp;have to explicitly write to a file or let it error on the client. May I see the VbScript (or a snippet of the VbScript)? 
 
Chris
</div>

<div>
yes,,,i can physically map a drive myself, but to show 200 users how to do this,,,its not efficient...i just wanted to map the drives that are used most so when users log on they are already there for them..all they would do is create a shortcut on desktop...which i am currently looking into also...so they really have nothing to do... 
 
as i said before they work fine on local subnet, but nothing shows up on remote sites...not even an error message or are you suggesting that it is getting an error message and that its just not being displayed on the desktop... 
 
 
Here is the other Script: 
 
Set objNetwork = CreateObject(&quot;WScript.Network&quot;) 
objNetwork.MapNetworkDrive &quot;N:&quot; , &quot;\\Server\Share&quot; 
 
once again thanks for your help!!!! 
 

</div>

<div>
 
The error won't display with Net Use unless we redirect it somewhere we can read it from. That is, it would show the error, but then it would go away because nothing makes the error stay around to be viewed. 
 
For VbScript we'll want to insert a bit of code. Do you have a line that says &quot;On Error Resume Next&quot; in there at the moment? If so, all we need to do is below :) 
 
Chris 

<pre><code class="code-10 nolinks" id="code-265991">' Get the temp directory
Set objShell = CreateObject(&quot;WScript.Shell&quot;)
strTemp = objShell.ExpandEnvironmentStrings(&quot;%TEMP%&quot;)
 
' Set up a log file
Set objFSO = CreateObject(&quot;Scripting.FileSystemObject&quot;)
Set objFile = objFSO.OpenTextFile(strTemp &amp; &quot;\LogonScript.log&quot;, 2, True, 0)
 
Set objNetwork = CreateObject(&quot;WScript.Network&quot;)
' Clear out any errors we might have so far
Err.Clear
objNetwork.MapNetworkDrive &quot;N:&quot; , &quot;\\Server\Share&quot;
' If an error occurred
If Err.Number &lt;&gt; 0 Then
 ' Write it to the log file in the Temp directory
 objFile.WriteLine &quot;Error mapping n: to \\Server\Share:&quot;
 objFile.WriteLine Err.Number &amp; &quot;: &quot; &amp; Err.Description
End If
</code></pre>
</div>

<div>
i do not have &quot;On Error Resume Next&quot;....is this something that i would put at the end of the script that i sent you in its own line and then paste the script you wrote into it...thanks,
</div>

<div>
 
Hmm in that case it should write the error back to the screen if it bumps into one. On Error Resume Next is used to prevent the script stopping when it encounters an error. 
 
Can we just check that the drives really aren't mapped? After the script has failed to do its job somewhere run: 
 
net use 
 
That will show you a list of all current connections. 
 
Otherwise, if the script consisted of nothing more than the lines you posted the full thing would be as below. 
 
Chris 

<pre><code class="code-10 nolinks" id="code-266005">' Get the temp directory
Set objShell = CreateObject(&quot;WScript.Shell&quot;)
strTemp = objShell.ExpandEnvironmentStrings(&quot;%TEMP%&quot;)
 
' Set up a log file
Set objFSO = CreateObject(&quot;Scripting.FileSystemObject&quot;)
Set objFile = objFSO.OpenTextFile(strTemp &amp; &quot;\LogonScript.log&quot;, 2, True, 0)
 
Set objNetwork = CreateObject(&quot;WScript.Network&quot;)
' Let us handle errors
On Error Resume Next
' Clear out any errors we might have so far
Err.Clear
objNetwork.MapNetworkDrive &quot;N:&quot; , &quot;\\Server\Share&quot;
' If an error occurred
If Err.Number &lt;&gt; 0 Then
 ' Write it to the log file in the Temp directory
 objFile.WriteLine &quot;Error mapping n: to \\Server\Share:&quot;
 objFile.WriteLine Err.Number &amp; &quot;: &quot; &amp; Err.Description
End If
</code></pre>
</div>

<div>
okay...did gpupdate /force on client machine to solve another issue and now the net use mapped drive is showing, but not the .vbs script one...any suggetions....
</div>

<div>
 
Did it manage to create us a log file in %Temp%? 
 
Otherwise, how are you referring to the script? Is it running from Group Policy? 
 
Can't ignore the possibility that it's simply not running at all :) 
 
Chris
</div>

<div>
i assumed the vbs script ran because it was showing up on local subnet
</div>

<div>
<div class="content wysiwyg-content">
hope someone can help. i know pretty much nothing when it comes to logon scripts..just enough to be dangerous..so here is my question... 
 
i wrote two logon scripts to map 2 shares for users of the domain on site A ...we have 2 DC`s at site A...both logon scripts work..it is mapped at each computer of the domain under the same subnet. 
 
we also have Site b,c,d,e,f all connected through MPLS Circuits...every site is on their own subnet...i can resovle DNS at every site..every site DNS settings are pointing back to site A DNS Servers..i even joined site (for now) B to the domain.... 
 
the issue is the mapped drives through logon scripts are not being mapped to the remote sites...only on the domain with the same subnet at site A...i can physically map a drive on the computer at site B, ,but not through logon scripts... 
 
is there something you have to do to get these logon scripts to work when dealing with computers of the same domain, but not all on the same subnet....here is list of subnets with sites... 
 
192.168.0. &nbsp;site A 
192.168.30. site B 
192.168.40 site C 
 
you get my point as far as how the sites are setup... 
 
any help woudl be appreciate....i search countlessly on google for answers and for me to start to learn scripting is just giving me a headache....any suggestions is appreciated...thanks,,,,
</div>
</div>

hope someone can help. i know pretty much nothing when it comes to logon scripts..just enough to be dangerous..so here is my question...

i wrote two logon scripts to map 2 shares for users of the domain on site A ...we have 2 DC`s at site A...both logon scripts work..it is mapped at each computer of the domain under the same subnet.

we also have Site b,c,d,e,f all connected through MPLS Circuits...every site is on their own subnet...i can resovle DNS at every site..every site DNS settings are pointing back to site A DNS Servers..i even joined site (for now) B to the domain....

the issue is the mapped drives through logon scripts are not being mapped to the remote sites...only on the domain with the same subnet at site A...i can physically map a drive on the computer at site B, ,but not through logon scripts...

is there something you have to do to get these logon scripts to work when dealing with computers of the same domain, but not all on the same subnet....here is list of subnets with sites...

192.168.0.  site A
192.168.30. site B
192.168.40 site C

you get my point as far as how the sites are setup...

any help woudl be appreciate....i search countlessly on google for answers and for me to start to learn scripting is just giving me a headache....any suggestions is appreciated...thanks,,,,

logon scripts across multiple subnets

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).