Drive mapping script on VPN 5

[Zamuk]

I have a SBS2k3. I have connected the laptop to the VPN and in authenticates. but, I'm unable to use net use \\servera\netdocs using CMD.
What is the correct script that I need to put in to connected to this server share?

Sever name = Servera
Share name = Netdocs

 

[djtech2k]

Do you get an error? That should work, but will be more difficult to access. I would do something like this:

net use Z: \\server\share

 

[Zamuk]

yeah, I get "System error 67 has occured. Network name can not be found".

I know for a fact that on the E: drive of Servera there is a share named Netdocs which all the LAN users have mapped on their computers. So I know that this is a valid address.

Anything else? I'm sure I'm missing something.

 

[Zamuk]

I have another laptop that I was able to configure it on the LAN while I was in the main office. When I'm on the road I can still go to My Computer and see the drive mappings that I configured while in the office. However, once I established a VPN connection, and I doubleclick any of those mapped Drives I get the following:

An error occurred while reconnecting T: to \\servera\shared files.
Microsoft Windows Network: The local device name is already in use. This connection has not been restored


Seperate issue? What can I do to resolve this one as well?

Thank you,

Zam

 

[djtech2k]

It sounds like a netbios or DNS problem. Can you successfully ping the server? Does your VPN connection have any port filtering?

 

[Sybje]

I agree with djtech2k... Try to connect the share, using the IP address of the server instead of the name...

If it works then, you probably don't have the right WINS server defined in the TCP/IP properties.

 

[1LUV1T]

Most likely its what Sybje says...
if serverA = 192.168.1.1
replace //serverA with //192.168.1.1

 

[Zamuk]

Tried the IP way... no good.
Now, once I established a VPN connection I did attempt to ping the server from my laptop. It timed out.

I did a ipconfig from the CMD and see that my VPN IP Address is 192.168.1.23, which is on the same network as the server (ServeA = 192.168.1.250)

The local network at this remote site is also a 192.168.1.x format as well....not that this would be hindering the VPN...but I thought I'd just throw this out there.

Also, I have found that this laptop is a Windows XP HOME edition. I know of it's enability to connect to a domain (server). Would this be a reason?


Regardless, I'm unable to ping the server @ 192.1688.1.250. what am I missin'?

Zam

 

[Sybje]

I think both sites with IP addresses in range of 192.168.1.x could be the problem here...

can you ping your gateway? Is that the same value on both sites?

If possible try to change the subnet on one of the sites...

 

[1LUV1T]

Your beating me to it Sybje

"The local network at this remote site is also a 192.168.1.x format as well....not that this would be hindering the VPN...but I thought I'd just throw this out there."

That might be your issue. Just test out changing your home IP to like 10.20.30.1 and then try to tunnel into your work.

 

[Zamuk]

yeah, I "suspected" this may be a problem. That's why I mentioned it hoping one of you folks would shoot that idea down and explain why. But, ya'll seem to be in accordance, so I'll do it on Monday.

Stay tuned......

 

[lhuegele]

Yes, your home network needs to be on a different subnet than that of your VPN. We had this same problem. Changing the home network's internal IP range to something other than what we have at the office cleared all the issues up.

Good luck.