One way to get around this issue is to set up your cisco router to use a split horizon. This allows you to see both networks. We currently do that here so that we can see our internal network and our customers network.
Tom -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, September 20, 2004 7:48 PM To: [EMAIL PROTECTED] Subject: Re: NT 4.0 SP5 w/ cisco VPN client Actually, what is happening is by design and quite correct. When you connect your computer by VPN (tunneling through the Internet to the NT server), your computer takes on a another IP which is a LAN IP of the network you're connecting to. The RRAS server will normally assign your computer a LAN address. You end up with two LAN adapters. One physical and one logical. The Physical one is a LAN card or a modem. The VPN connection on your computer will ba a logical network adapter. Once the VPN connection is established, access the VNC4 server using the server's LAN IP address and not the public Internet IP address. At 18:47 20/09/2004, Adam Jongewaard wrote: >I have a Windows NT 4.0 SP5 machine and am trying to run the VNC 4.0 >server on it over a VPN client. I know that the VNC server is supposed to >run on all available IPs but I put my mouse cursor over the systray icon >and it only shows my public IP, not my private VPN IP. >Am I missing something? Is there any way for me to tell VNC that I want >to use my private VPN IP? or am I out of luck? >It does work fine that way for XP but my server machine is NT and a long >long ways away so I need to get it working if at all possible. >Adam _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
