![]() | ![]() |
|
Welcome to the HEXUS.community discussion forums forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and other features. By joining our free community you will have access to post topics, respond to polls and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! |
|
|||||||
Networking and Broadband ADSL, cable, internet and network advice and chat ![]() |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Puk Guy
Join Date: Mar 2004
Location: Cardiff and Brum
Posts: 824
Thanks: 0
Thanked 0 Times in 0 Posts
|
Remote Desktop help with IP address
...before we start, I don't want to install anymore 3rd party remote networking software like VNC or Remote Admin, I just want to concentrate with Remote Desktop atm.
OK....I've used Remote Desktop before, accessing me missus's PC via mine, and I know the basics on how to set it up. But now when it comes to accessing my own PCs I'm having some problems. Remote access is set up already. My DSL connection is done via a Netgear modem/router, with 4 PCs attached to it. When I type IPCONFIG /all, which IP address do I need? As each PC is attached via the router, its auto assigned an IP like 192.68...... but what are there unique IPs and what is my connection IP? Once I have these 2 bits on info, how do I connect to it? Do I enter the connection IP followed by the network IP (213.xxx.x.xxx:192.168.......)? And if I was to remote access from one of the network PCs to another, do I just type the network address? Or do I need the connection IP as well?
AMD3D under reconstruction.....new forum design
|
|
|
|
|
|
#2 (permalink) |
|
More l33t than dangel
Join Date: Jul 2003
Location: /dev/urandom
Posts: 13,337
Thanks: 27
Thanked 252 Times in 199 Posts
|
internally, just connect to the ip of the machine in question (e.g. 192.168.0.133)
externally, you've got to set up some port forwarding to get this to work, unfortunately. since all your pcs have internal (192.168) addresses, their internet connection is shared across one ip (213, whatever), and you CANNOT access the individual machines behind this NAT system directly. what you CAN do is ask that certain ports get forwarded - for example, any connections on port 23 to 213.x.x.x get forwarded, transparently, to something like 192.168.0.16. in this case, the port is 3389 for windows terminal services (rdp). in your router config somewhere you can ask that all connections to your adsl's ip (213.whatever) on port 3389 get forwarded to the internal machine of your choice (192.168.whatever). the downside of this is that you can connect to one machine, and one machine only, from the outside, by connecting to 213.whatever. what you CAN do though is daisy-chain things - port forwarding lets you access machine 192.168.0.2 from the outside, run the terminal server connection on 192.168.0.2 to allow you to connect to any of the other machines inside the network. i'm not making much sense am i |
|
|
|
![]() |
| Breadcrumb | ||||||
|
||||||
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Missing LG DVD remote | jcoquillon | Audio/Visual - Standard and HD | 5 | 22-03-2004 10:06 PM |
| Missing a MAc address | Gordy | Networking and Broadband | 6 | 24-02-2004 04:39 PM |
| WinXP Remote Desktop | acidrainy | Networking and Broadband | 1 | 10-01-2004 11:38 AM |
| How to change your email address at Play.com | PanzerKnight | General discussion | 2 | 30-12-2003 08:59 PM |
| list@hexus virus spam | Swafe | Operating systems & applications | 16 | 24-08-2003 02:51 AM |