After the VPN is up you should be able to connect to the printer by its real
IP address on the other network. Then you can set it up as a printer on the
server in the normal way.
Anthony,
http://www.airdesk.com
<(E-Mail Removed)> wrote in message
news:22911099-dd4d-4621-a44f-(E-Mail Removed)...
> This question may be more appropriate for the Terminal Service group
> but
> will try here
>
> We have a Windows 2003 Terminal Server setup at our main office. It
> is
> also a DC and DHCP Server -I know, bad idea. Our remote office will
> connect to the main office via a VPN using Static IPs at each office,
> using router-to-router IP-SEC.
>
>
> The main office uses 192.168.1.xxx IP addresses from the DHCP server.
>
>
> We have a TCP/IP - based Canon IR-2270 printer/copier at our remote
> office that WYSE thin-clients will print to when using the
> application
> on the TS at the main office. The thin-clients get their IP addresses
> from the router there - there is no server here. Our VoIP provider is
> setting up the VPN and has not yet provided us any details on its IP
> structure.
>
>
> So, when we install the Canon driver on the TS , and choose
> Local>Create Port, what IP address should the printer have? Would it
> be a 192.168.1.xxx or one based on the IP structure at the remote
> site? The printer wizard will prompt us if it cannot find the printer
> on the network, and obviously it will not have a chance until the VPN
> is setup.
>
>
> There is a third-party vendor "installing" this printer and we want
> to
> tell them to go ahead and add a static IP address to the printer -what
> are the possibilites here?
>
> Thanks!
>
>