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

unable to connect to networked printer when connected to vpn 1

Status
Not open for further replies.

jaydo1

Technical User
Aug 1, 2004
12
AU
Hi can any body please help I have a printer connected to a pc on lpt1 (and shared off)and an other pc which uses this printer over the network both machine connect to vpn's.When not connected to the vpn's both pc's can print to this priner. When connected to the vpn the pc that uses the printer over a network share cannot print.I have tryed using net use but it still can't print .Is the any way of finding where the problem is or is it inpossable to use this printer when either of the pc's are connected to the vpn.
 
It's because you have the "Use default gateway on remote network" un-checked on the VPN properties. The downside is that you will no longer be able to reach your local LAN subnets as it will use your Internet default route to get to those subnets. If applicable to your network, you need to add static routes to the computer using the route add command for the local LAN subnets you need access to.

 
Two possible problems and their resolution:

1. You use the same private IP subnet and subnets masks on both your local LAN and the remote LAN.

The first potential reason you are losing connectivity to your home printers is because of the infamous "double nat" problem. The standard IP address range that the DHCP server built into many small routers is 192.168.1.0/24. It is possible that your office network serves addresses from the same subnet and is NATing those addresses out the Internet. Once a VPN connection is established from your PC, typically the clients learn routes to the central office network over the tunnel and when your PC is trying to access the printer for your local LAN network the traffic is really going out towards the corporate network because that route will take precedence. The simple solution to this problem is to simply reconfigure your router to provide IP addresses to your PC's and printers that are not from the same subnet that may exist in your corporate network.

2. See Step #4: MS KB
2b. You might consider the use of LMHOSTS (it seems unlikely a WINS server is inolved in this setup).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top