VPN and network browsing

[J741]

I control a Windows NT 4.0 server in a small business network. One of the users needs to be able to acess the server's data from the user's home. The user has a broadband internet connection at home. I set up RAS on the server, and VPN on the user's home PC (Windows 98). The user can VPN in to the server, and then PING the server, but can not browse the office network or access anything from the server. Even "find computer" can not locate the server by name (even though it responds to PING requests).

Now as I understand it, the user must log-off of Windows after the VPN connection is established, and then log-on to the Windows NT domain (which he can not do until the VPN is active). This is a real pain in the @$$, and this non-technical user can't seem to follow my instructions enough to do this.

So, is there some way to force the Windows NT server to see the VPN login as a Windows NT domain login? Or is there a way to reduce the Windows NT security to allow access to users who are not logged in to the Windows NT domain (security is not an issue for this inquiry)?

If any one can tell me how to make this really simple for the non-technical Windows 98 user, I would greatly appreciate it.

 

[djhawthorn]

Err, backtracking, is RAS set to "Allow access to this computer, and the entire network" or just "Allow access to only this computer"? MCSE NT4/W2K

 

[J741]

It is set to allow either TCP/IP or NETBEUI protocols, and allow entire network access.

 

[J741]

I thought I had found a solution...

I stumbled across some command line options that I thought might help if I put them in a batch file to be run after the VPN connection is established.

I thought that I could use the "net logon" command after the VPN is established, but it just returns the error message "you cannot do this from within an MS-DOS window"

Damn!

Oh, and I did find a solution to the browsing issue. It seems I needed to share a resource on the client machine before it would see anything in "network neighborhood". This seems damned strange to me, but now it can at least see the server (but can not access anything on it, or see other machines on the office network).

WHINE: What use is the "log on to network" checkbox in the VPN client configuration if it doesn't actually log you on to the network !?