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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPNXP Pro to SBS / Exchange

Status
Not open for further replies.

mattpage

IS-IT--Management
Apr 20, 2004
9
GB
Hi all,

Been looking at these forums for a few days now but still can't resolve our VPN problems.

We have in the office a SBS 2000 Server with Exchange 5.5, this is connected to the internet via a router on an ADSL connection. VPN port is open on the router for forward to the SBS server.

The client end is a laptop with XP Pro and a standard BT dialup connection.

The user CAN connect via the VPN, user is authenticated and shows up in the Remote Access on the server. An IP address is assigned through DHCP (one of the ones with a telephone icon).

However the client can not browse the network OR ping the SBS server (192.168.32.10).

The IPCONFIG settings for the client show the Server IP and Client IP as 192.168.32.102 (which is assigned for remote access in SBS)

There is a WINS server running (192.168.32.10) and enabled in the VPN connection, and LMHOSTS have been setup on the client.

Basically in the office everything is sitting on the same server, WINS, DHCP, Remote Access and shared files(192.168.32.10)

When looking at 'Entire Network' on the client they can see the DOMAIN but there is nothing else (no server or shares).

I hope this is enough info for someone to help, if not I can post some more....

PS... Apparently it sometimes works, maybe 1 in 10 attempts, but I have never seen it working so I can't be sure.

Thanks

Matt.
 
first thing first. you need to make sure you can ping the server. it could be the NAT or ISA block the ping or restrict the access.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at
 
Can't ping the server (192.168.32.10) from the VPN client but it can ping itself on the addresses assigned (192.168.32.102), but that is just routed to localhost anyway...

The plan now is to convert one of the office PCs into a dedicated VPN server and see if that helps with anything. There is soo much happening on one machine it is getting difficult to debug.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top