Connected .. Now what?

[Cogen]

Hello everyone.

I have recently configured a VPN server in my work office. I can connect to that VPN server from outside the office, but my problem is that I don't know how to access files on the server.
The whole point to me setting up the server is so that all of the company employees at different offices can connect and store files on it. I have setup user accounts and I created a shared directory under C:\. I was hoping that once I connected to the server through VPN, I would be able to see the shared folder in "My Network Places" from the client machines. Please help.

 

[John Lewis]

What are you using for a server? Sounds like you have a workgroup setup (no domain)? Do you have a 'server' version of Windows running (or a linux box with Samba)?

If your routing is OK, you should be able to connect to server side resources from the client by typing
'net use f: \\serverIP\ShareName' in a command window.

That assumes f: is not otherwise in use on the client. The serverIP is the IP address of one of your machines that is setup to share a folder, not necessarily a server version of Windows.

You should verify basic connectivity first, open a command window and try 'ping serverIP' and press enter.

The Network Places browsing does not work because the list of computers that are available does not pass across your VPN connection. There are ways around it, but none that works in every situation. If you have W2K server or Samba, best bet is to setup a WINS server, so post back some more details.

 

[Cogen]

Thank you for the reply mhkwood.
-I have a Windows 2000 Server I'm using as the VPN server.
-When I type net use f: \\serverIP\ShareName , I get System error 67 (The network can not be found). f: is not in use on the client.
-When opening the cmd prompt on the client, I cannot ping the actual external IP address of the server, but I can ping the servers internal IP ... ping 10.100.200.1 works great. I also am able to tell that the server gave me 10.100.200.8. I also can confirm that I'm connect because it shows me as connected in Routing and Remote Access->Remote Access Clients(1).

More details ...
-I have a domain setup called wecore.com. All of the user accounts are part of this domain in Active Directory. When I login to the VPN, it doesn't seem to make a difference whether I login as username, or username@wecore.com.
-One strage thing that I wasn't expecting is that once I connect to the server over VPN, and cannot browse the internet anymore using IE, or even ping a website (like ping

http://www.google.com)

 

[Cogen]

Okay, I got it working a little. I reconfigured the RRAS, and now I can connect and successfully type 'net use f: \\serverIP\ShareName'. After that I have to type my username/password in again, but as long as I do that, I can then view the shared folder in Windows Explorer under F:.
The one question that I have is ... is there a way around having to type 'net use f: \\serverIP\ShareName'? It's not problem for me, but I would rather not make every employee have to do that on their machinces.

 

[John Lewis]

The supported method would be a WINS server. MS has bounced back and forth about where the WINS server should reside, some docs say it has to be on the VPN server, some say it can't be on the VPN server. If you only have one server box, that's where you have to start. I generally use a linux box for VPN server and WINS server without any problem.

Set your connection to use the WINS server and give it a try.

That's on the connection properties, networking tab, highlight TCP/IP and click properties, click advanced, (while your there, unmark the box that says 'use default gateway on remote network' -- you should be able to surf again), then click the WINS tab and add your server.

 

[Cogen]

Thanks mhkwood, you've been a huge help. I'll read into WINS and see if I can get it working on the same box/server.

 

[jimtheone]

- Use the same WINS server as you use for your company and It should work fine.
- Make sure the default gateway for internal Network Card is blank.

 

[LSV]

if a mapped drive works for you (ie: net use f: \\serverIP\sharename) and you're just looking to simplify access for other users, perhaps you can automate the mapping for them.

Ie:

create a batch file that will perform the NET USE function, email to them and have them run it whenever required.

All they have to do after that, is open F: from "My Computer"

Worked for a client of mine...

-Cheers.

 

[SNAPC]

Good Day,

The TCP port #139 must be enabled on your firewall to allow NetBIOS traffic to pass to secure file share and printer share connections.

Best Regards,

Keith Woodard
IBM Rational Tool Consultant