Re: Tunnel to Network Printer
- From: "Postmaster" <postmaster@xxxxxxxxx>
- Date: Tue, 07 Mar 2006 17:09:17 GMT
"Buck Turgidson" <jc_va@xxxxxxxxxxx> wrote in message
news:lhq0e3-0aq.ln1@xxxxxxxxxxxxxxxxxxx
Having seen this before, my solution was to add the IPX protocol
back into the Windows boxen. Although some VPNs may
decide to muck with the IP routes, they usually don't
tamper with other protocols. :-)
Add the IPX protocol to the Windows clients, and the Windows
boxen that has the printer. Reboot the Windows boxen and
start the VPN. In my case, the printer is now working fine
while the VPN is up. (Without IPX, it became inaccessible, but
adding IPX routed nicely around the VPN route table hacking.)
When you say add IPX to "the windows box that has the printer" do you
mean the box to which the printer is attached? If so, it is a network
printer, and it is just connected to a Linksys router.
Thanks.
Buck,
Add IPX to the Windows client, then reboot, start the VPN,
and see if you can still see the printer. It works for me.
Hopefully, the network printer will support IPX and pass
it through the Linksys router. If so, you should be a happy
camper.
Enjoy,
Postmaster
.
- References:
- Tunnel to Network Printer
- From: Buck Turgidson
- Re: Tunnel to Network Printer
- From: Chris Davies
- Re: Tunnel to Network Printer
- From: Postmaster
- Re: Tunnel to Network Printer
- From: Buck Turgidson
- Tunnel to Network Printer
- Prev by Date: Re: Tunnel to Network Printer
- Next by Date: Arrrgh! rsync "chroot failed" error message!
- Previous by thread: Re: Tunnel to Network Printer
- Next by thread: Re: Tunnel to Network Printer
- Index(es):
Relevant Pages
|
