The VPN server is Win 2003 Server SP1 with Wingate 6.2.0, no other known problems seen.
LAN is on two subnets; 192.168.0.1 for wired and 192.168.1.1 for wireless. These work OK; able to browse, see shares, ping, etc. amongst all machines in here.
WAN is on two fixed IP adapters. One is the internet gateway adapter; other is for the VPN. The server runs IIS with sharepoint and also terminal services. Again, no problems are encountered in here.
Wingate runs NAT plus email SMTP, POP, IMAP servers with no problems. The NT user database is used, and NTLM authentication is enabled for the various mail servers. The ENS policies are open to all (don't need restrictions here).
The VPN is set to accept authenticated members of Administrators.
OK, so when I connect to the VPN from a client laptop (Win XP Pro), I get the negotiated VPN connection right away. There are no routing conflicts; all of the LAN computer names are there; those that are actually present stay enabled.
From here I'm stuck -- I can't browse them, and I can't ping them. Ping returns "Ping request could not find host abcdefg." NETBios over TCP/IP is on, and MSoft printer / file sharing is enabled for the client.
I'm not sure I want to enable printer/file sharing at the server. And shouldn't the VPN just pass such traffic through anyway on its own ports?
It's not clear from the other posts in here whether Win2003 server does or does not include, either by default or after manual installation, RIP2, nor where to find it if it's there (I've looked in Add/Remove Windows components and its not there).
There is some mention of RIP in the context of setting Win2K3 up for DHCP, DNS, NAT, etc, but that's what I'm using Wingate for in the first place.
Any suggestions? The way things are now, I'm forced to come into the server on a remote session, then initiate a nested remote session to get to an inside computer, to do things (print, that I'd like to do directly by VPN.
Thanks,
John