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

Can connect to VPN but cannot browse

Status
Not open for further replies.

DezUk

Technical User
Jul 18, 2003
18
GB
Hi

At work i have recently been given an account to logon to the company VPN. I have installed CheckPoint Secure Client with a pre setup policy. I can connect to the VPN with no problems but once connected i can't ping any of the PCs at my office.

Im using a SMC 7008 router at home and connecting to a Nokia IP440 at the office end.

I know that something is definately wrong at my home end because if i connect to anotrher network in my office bulding i can connect to the VPN fine.


Software im using:

Windows XP Pro SP2
CheckPoint VPN-1 Secure Client Build 023
Avast Antivrus


Thanks for the help :)
 
Are you sure the firewall isn't blocking ping's?

Iain
 
Yea im sure

When i connect to the different network at my office i can ping pcs over the vpn with no problems.

I also cant connect to any mapped network drives or print to any printers in my office.
 
You said "When i connect to the different network at my office i can ping pcs over the vpn with no problems" maybe this VPN policy allows ICMP thru the VPN but the VPN policy from outside of your office like your home does not allow ICMP in to the network. Can you browse the network by mapping shared drives etc... If not I would ask the network admin to check for the VPN policy for what is allowed and what is being blocked.
 
This could be a NAT issue, especially if NAT traversal is not enabled on the VPN server. When you connect from home, can you do *anything* with the office?

A good way to test this would be to remove the home router and attempt to connect without it. If you can connect and everything works, then the router was the source of the problem.
 
If your connecting to 2 different networks at the office does that mean 2 different subnets?

If you have a NAT IP at home it could be the same subnet as work and that will throw odd problems like this.

Iain
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top