I would like to access my desktop at work using VNC. But it is behind a cisco NAT Router?
481853
pretty simple actually, the command would be:\n\nip nat inside source static tcp <PRIVATE_IP> 5900 <PUBLIC_IP> 5900\n\nIf using VNC with web browser:\n\nip nat inside source static tcp <PRIVATE_IP> 5900 <PUBLIC_IP> 5900\nip nat inside source static tcp <PRIVATE_IP> 5800 <PUBLIC_IP> 5800
20878
I'm assuming that your desktop is connected to an Internet modem (cable or DSL) via an Ethernet cable.\n\nYou need:\n1.  A wireless Internet router (preferably the kind with a few wired ports as well)\n2.  A network printer server\n3.  One Ethernet cable (between the desktop and router)\n4.  You may need a new printer cable between the printer server and printer\n\nI recommend disabling SSID broadcasting and enabling encryption on the router, and setting up that encryption on the wireless laptops.
7199
There are many ways you can do it.\n\nIF you are in a corporation, you may want to talk to the IT administrator first.\n\nYou can do it free by using Windows XP Pro on the host machine with "Remote desktop."\nhttp://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx\n\nAnother free program is called VNC. Same idea, but you can run it on any type of computer. Mac, Linux, or Windows interchangeably. I use my Powerbook (Mac) to access my Windows computer at work. It's open source, and there are more variants out there. Just search it on Yahoo! Search.\n\nhttp://www.realvnc.com/\n\nOther versions are not free and include, http://www.netopia.com/software/products/tb2/\n\nand \n\nhttps://www.gotomypc.com/en_US/entry.tmpl?_sid=59863154%3AC51ECA837DF4C94&Action=rgoto&_sf=2
47750
You have a couple of options here.\n-Windows XP-\n-Option 1-\nYou can select the remote assistance option from the start menu and follow the on screen prompts in order to send a connection file from her machine to yours. Beware this will not work if she is behind a home router ( due to a non routable IP address)\n-Option 2-\nYou can open remote desktop providing you know her IP and you have allowed remote desktop connections.\nStart > Run > mstsc then select OK.\nTo enable remote desktop right click on "My Computer" and go to properties and then select the remote tab then check the allow remote connections to this computer box.\n\nAdvanced\nYou can research RealVNC or any other form VNC out there since it is open source software.
207429
XP Home doesn't have the Remote Desktop server capability.  XP Home can be a client (controlling an XP Pro machine), but it can't be a server (being controlled by another machine).  For that, you can use a program like VNC, free from http://www.realvnc.com . \n\nThese tips should help you get the computers to see each other: \n\n\n1. If the computers run the original or SP1 versions of Windows XP, disable XP's built-in Internet Connection Firewall on local area network connections -- it's for use only on a direct modem connection to the Internet.  If they run SP2, enable the exception for file and printer sharing in the Windows Firewall.  Disable and un-install all \nother firewall programs while troubleshooting.  When un-installing a firewall program, use the un-install procedure provided by the \nmanufacturer .  Don't use Control Panel | Add or Remove Programs, which might not completely un-install it. \n\n\nFor more information, see: \n\n\nWindows XP Internet Connection Firewall \nhttp://www.practicallynetworked.com/sharing/xp/ic_firewall.htm \n\n\n2. Use only one protocol for File and Printer Sharing.  If the network needs more than one protocol, unbind File and Printer Sharing from all but one of them.  Details here: \n\n\nWindows XP Network Protocols \nhttp://www.practicallynetworked.com/sharing/xp/network_protocols.htm \n\n\n3.  Make sure that NetBIOS over TCP/IP is enabled on all computers. Details here: \n\n\nEnable NetBIOS Over TCP/IP (NetBT) \nhttp://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm \n\n\n4. Run "ipconfig /all" on XP and look at the "Node Type" at the beginning of the output.  If it says "Peer-to-Peer" (which should actually be "Point-to-Point") that's the problem.  It means that the computer only uses a WINS server, which isn't available on a peer-to-peer network, for NetBIOS name resolution. \n\n\nIf that's the case, run the registry editor, open this key: \n\n\n   HLM&#92;System&#92;CurrentControlSet&#92;Services&#92;Netbt&#92;Parameters \n\n\nand delete these values if they're present: \n\n\n   NodeType \n   DhcpNodeType \n\n\nReboot, then try network access again. \n\n\nIf that doesn't fix it, open that registry key again, create a DWORD value called "NodeType", and set it to 1 for "Broadcast" or 4 for "Mixed". \n\n\nFor details, see these Microsoft Knowledge Base articles: \n\n\nDefault Node Type for Microsoft Clients \nhttp://support.microsoft.com/default.aspx?scid=kb;en-us;160177 \n\n\nTCP/IP and NBT Configuration Parameters for Windows XP \nhttp://support.microsoft.com/default.aspx?scid=kb;en-us;314053
475513
If you are using windows xp with service pack 2, using Remote desktop you can control.\n\nOtherwise use symantech's PCAnyware
252053
I am assuming that you are using Windows XP.  First of all, make sure that you have configured your machine to allow remote desktop access.  Right-click on "My Computer", click on the "Remote" tab, then make sure that "Allow users to connect remotely" (in the Remote Desktop section) has been checked.\n\nNext, make sure that if you are using any firewall software or your machine is connected to any type of router that is blocking ports that you open up port 3389, which is the remote desktop port.\n\nIf the machine is given an internal IP address using Network Address Translation (NAT) and your machine isn't the one with the exposed static IP, then make sure you set up port forwarding services on the router to go to the correct IP address of your machine on your internal network (use IPCONFIG on the machine you wish to connect to in order to get this) and forward requests to port 3389 to that machine.
227153
Well.........you might consider retyping this so that it is a little easier to understand but, if I were to give an educated guess at what your asking, it sounds to me that you want to access another computer remotely? If that's the case then you will need to give access in your firewall settings. If you have Windows Firewall, go to Start, Control Panel, Network Connections then click on the connection you need to access once then click "Change Windows Firewall settings", then click "Exceptions" and check the box that says "Remote Desktop" and also "Remote Assistance" then click "Advanced" click on the connection that you are accessing and click "Settings" and then check the box that says "Remote Desktop" This should give you access. If you are using another kind of firewall(other than Windows Firewall) you will need to go to their web site and get instructions.
354148
It's generally not possible to get the IP address of a computer that is behind a NAT firewall.  It would be rather useless anyway as you could easily have many sessions coming in through NAT'd connections that have the same IP address.  For session control, you'd be far better off using a session cookie.
620664
what you want to do is to use NAT.  what this does is make all traffic from your lan look like it's coming from the same IP, each connection using a different port. example: 1 server connected to the net w/ 1 pc in the lan:\n\npc1 wants www.3atm3.com's webpage and sends a request from 1.1.1.1 to the NAT box 1.1.1.2, which sends the info to the net saying "1.1.1.2:1234 looking for www.3atm3.com", when the page comes back it will be for port 1234, and the NAT box forwards the info to 1.1.1.1\n\nI'm not giving you a set-by-step to set up a NAT, but the idea is that:\n1) lan pc's use the NAT server as their gateway...done\n2) NAT box is configured to route traffic and knows it is doing NAT for the LAN\n\n...use a linux box for the NAT server- it's easier
34048
VNC is a great open source remote desktop program.  There is a server part for the slave and a client for the master.  It is password protected and can be run through SSH for encryption.  Will work over a netowrk not sure if it can work over the internet though.  That's a whole other ball of wax.  GoToMyPC.com is for internet remote access.
1003981
Try this... It got mine running!!\n\nhttp://compnetworking.about.com/od/vpn/ht/newvpnwindowsxp.htm
261203
Sure.\n\nWhen your connected to something, go to your start menu, and click RUN.\n\nOnce you have run open, type "CMD".  This will open the command line.\n\nThen while in command line (This is a black rectangular window).  Inside this window, type "netstat".\n\nFine the port and program that you are looking for, and voila! You got their IP.
244855
You will have to install your isp data.  The same cd you used with your desktop will work with your laptop.  But if your connection to the laptop is going to be wireless, then most of that will be done automatically and there will be no need to use that cd.
543699
You can only add other LAN PC's or webfolders configuration to "My network places". It would be better to add yahoo as a shortcut to your desktop.
921320
Try using http://www.vtunnel.com/ and see if you can use the ip tunnel to get around it.
871646
The cheapest way to go is to just plug into the Ethernet ports on the router. Of course the desktop must be fairly close to the router and have an Ethernet NIC. Why introduce the difficulties of wireless unless needed, the Ethernet connection will be much stabler. You can network a win98 and winxp machine with few difficulties either way.