Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Browsing Internal Network on VPN 2

Status
Not open for further replies.

aealba

MIS
Joined
Mar 18, 2004
Messages
2
Location
US
Would appreciate some feedback on the following situation. Small Windows 2000-based network (3 servers: 2 domain controllers, 1 RAS), 50 workstations behind Watchguard router; RAS has 2 NICs with Terminal Services pointing to LAN NIC (no default gateway) and VPN (PPTP) pointing to VPN NIC, Terminal Services works beautifully, VPN connection is established and authenticated but unable to browse internal network, can PING virtual VPN server and all internal nodes, VPN client registers in WINS servers (activated on both domain controllers). Will change VPN client network ID tonight (renaming workgroup and domain suffix). NetBEUI is not installed anywhere on network.

 
aealba,

I think you're saying that your VPN client can ping LAN machines. I'm guessing only by IP, not by hostname? At any rate, what happens when, from the VPN client machine, you run NBTSTAT -a on the IP address? (i.e. nbtstat -a 192.168.1.1 (use real IP)) You should get a netbios name response if NetBIOS is making it through the VPN. If you do get a response, what happens when you hit "Start" "run" "//computernamefromnbtstatcommand"? Also, "Start" "run" "//192.168.1.1" (use real IP)?
 
Just to clarify gacollier's post, I believe the command for netbios resolution is NBTSTAT -A (capital A not lower case)

and to access the server via the run command use the \\ slashes not the // slashes...

=)

no offense to gacollier, just a re-clarification!

Thanks
Chance~
 
OverDrive,

No offense taken, you're right on the money... my bad.

Thanks!
 
Thank you to both gacollier and overdrive - I was in fact using IP address to PING. I will pursue issue of NetBIOS resolution. Just to update situation: following changes to client(workgroup name, domain suffix), I was able to access shared drives using "\\servername\sharename". In other words, user was able access to required folders. My thanks to you both for your assistance - this was my first exposure to Tek-Tips.
 
Tek-Tips RULES!

If you find any tips helpful, there is a link for "Thanks "whomever" for this valuable post"

Make sure you thank the person(s) if they helped you out on the post!

Thanks and Welcome!
Chance~
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top