ICS out fine from client, RDP in to client no

July 26, 2009 at 12:16:28
Specs: Windows XP
I have 2 windows XP Pro SP3 systems, "A" is connected to the net through a router to a switch to the cable modem, "B" is connected via a crossover cable to "A" and connects out to the internet via ICS in "A" just fine. I need to be able to RDC to both of them because they are going to another house where there is only the cable modem, no hub, no router,just the cable modem and I don't want to spend any more of their money then I have to. Now here is the strange part, I have two static IP's, two separate internet connections so I can easily test across the net. I can RDC into "A" just fine, but not to "B" through the ICS connection. I can RDC to "A" and in "A" start another RDC to "B" from within "A" and voila, I have connection across the net to "B", but only by running one remote desktop connection from within another one. That works OK but it is inelegant and I know I should be able to RDC directly to "B" through the ICS connection in "A". I changed the listening port for RDC in "A" and "B" and believe I have the router and NAT set correctly. Both of my IP's come out of my cable modem to a switch and I can't make this work even when I connect "A" to the switch and let it get a dynamic address and just bypass the router entirely. I also believe that I have the firewalls set properly also but even when I turn them off I can only RDC to "A and then RDC again in "A" to "B". I can get to "B" for future needs on the part of my friends (The "B" machine is for their 11 year old who destroyed the "A" machine by using P2P software and getting many viruses, I had to wipe and reload from scratch.) This is driving me nuts!!! There is an ICS bug in XP Pro SP3 that there is a hot-fix for and I installed that on "A" but supposedly do not need to on "B". Can anyone tell me if I am wrong there? I do not want to do anything to destroy the connections I have managed to achieve. I would appreciate anyone who could tell me how to RDC directly to the "B" machine without having to nest RDP connections, even though that works. Thank you very much and I apologize for the long post but this is pretty complicated. Thank you in advance. MeadMaker.

See More: ICS out fine from client, RDP in to client no

Report •


#1
July 26, 2009 at 12:48:58
And how are you forwarding NAT traffic to B? You setup a port forward on a different port to map the secondary RDC connection?

IE - 3389 on your public NAT interface goes to A:3389 - and you have some other port (say, 3390) forwarding to B:3389 - is that right?


-I do not want to do anything to destroy the connections I have managed to achieve.

And you're putting this in a remote location? Hopefully you're not the guy they're going to be calling when it breaks, heheh. I'd opt for a swtich and get rid of the ICS, personally.


Report •

#2
July 26, 2009 at 12:54:25
correct, different port forwarded to "B" in router and ICS host and allowed in the firewall. I am trying to save them some money and now it is personal, I want to win this one!!!

Report •

#3
July 26, 2009 at 13:19:12
I'd verify the port opens on the remote site - can you telnet (or nc) to port 3390 from your remote connection & the TCP connection opens or no?

If no then it's got to be a routing issue on A if the NAT gateway works ok. You could verify that by installing Ethereal/Wireshark and looking for 'port 3389' traffic in the capture filter - verify the RDC packets are actually coming INTO A and weather or not they leave A on the other interface.

Sorry I don't know much about how ICS is routing any of this traffic - I've never used it personally. But if you do the above, it would at least prove the problem lies w/ ICS (or at node A).

If you can't get the secondary RDC forwarding going - my workaround would be to install cygwin, then install the SSH server: http://lifehacker.com/205090/geek-t...

After SSH is installed on A you can tunnel traffic through it using PuTTY. Localhost port 3390, remote: B's ip address:3389 - then you can RDC to localhost:3390 and traffic is tunneled through SSH. This is more of a linux solution though - cygwin makes the whole thing work on Windows, heh. That'd be my workaround if ICS won't cooperate.



Report •

Related Solutions

#4
July 27, 2009 at 13:41:15
I don't know from Telnet, how would I do that please?

Report •

#5
July 27, 2009 at 13:47:00
Can't telnet to anything on that network, would I have to open those ports in NAT, firewall, ICS also?

Report •

#6
July 27, 2009 at 13:53:58
I do have a workaround, I just nest RDP connections and that works fine. Thanks though, I appreciate your effort.

Report •

#7
July 27, 2009 at 14:42:08
How is ICS going to prevent the 11yr old from trashing both his pc and the ics pc?

A router that prevents p2p software and instant messaging, properly configured would prevent these from being trashed.


Report •

#8
July 27, 2009 at 14:58:18
They don't have a router and I am trying to save them a dime. Am I being penny wise and pound foolish here?

Report •

#9
July 27, 2009 at 15:02:02
Wanderer, what router would you recommend and how, please can I stop P2P and IM's?

Report •


Ask Question