Well, problem is fixed... read on for more information. No, I understand the principle behind the VPN tunnel. I know there are basically 2 nic adapters, one real and one virtual. The problem lies in the implementation of VNC in NT 4.0 vs NT 5.1 (XP).
On one laptop (XP), I run a VNC server when I am connected to my Cisco VPN client. A mouseover of the VNC Server systray icon displays both my private IP (VPN) and my public IP. On the other laptop (NT), in the same scenario... I am running a VNC server after I connect via my Cisco VPN client. The mouseover of the VNC Server icon in the systray only displays my public IP, no private IP. We use Remote Assistance for our XP clients and pcAnywhere for our NT clients. This guy had NT but for some reason the baseload he got didn't have pcAnywhere so I was looking for an alternative. We use the Blackice firewall client on all our laptops for protection but have ports enabled for both pcAnywhere and Remote Assistance to work when connected with our VPN client. I had quite simply forgotten that fact since I never have to disable the firewall when our users are connected to VPN. Long story short, disable blackice and VNC works like a charm. Made no difference that the private IP wasn't being displayed on mouseover... still detected and advertised on all IPs. To just make a quick u-turn. Is there some type of barebones VNC setup that we (I) could use here at work when we run into problems with pcAnywhere/Remote Assistance? I know that I can make a setup answer file to deploy with the package but I'm really looking for some type of barebones install that installs the server only (not as a service, client, icons, and even some default port changes, etc). Thanks again for all your thoughts. > 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 _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
