The same subnet???

[apex1x]

I've recently set up a VPN server and people can connect fine and I can ping them but we are unable to browse each other's files or see each other in LAN games.
I noticed that although the IP's were in the same range, 192.168.0.XXX, the subnets were different. 255.255.255.0 and 255.255.255.224

The first subnet is the one of the VPN server (Win 2k) and the second is from a WinXP comp, which connects VIA internet.

Might be incredibly simple to answer but I'm open to suggestions, thanks.

If you can understand it, you probably don't.

 

[ChicagoTechNet]

quoted from

http://www.chicagotech.net

Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN server, and you attempt to connect to a computer using a PPTP/VPN client, you may experience following problem: 1) The NetBIOS name of the computer to which you are attempting to connect is not resolved. 2) You may receive an error message similar to the following error message: "System error 53 has occurred. The network path was not found" when using net view or opening Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you attempt to connect to a computer using a PPTP client, you may be able to connect to computers on your local area network (LAN), but you may be unable to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server and clients.
2. If this is domain network and the WINS server is on the same computer as the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try to enable UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use UNC to connect to the remote resources by ip, for example, use the net use h: \\serverip\sharename command.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[gacollier]

apex,

255.255.255.224 is a standard VPN client subnet, so there's no problem there. If this was the problem you wouldn't be able to ping the computers on the LAN from the VPN client side. It sounds like name resolution is your problem. Do you have a "WINS" server on this network? Also, you might try using the "NBTSTAT" command to verify that NetBIOS packets can cross the VPN link.

Let us know what you find out.

Greg