MS RDP lol

[Anton Afanasyev]

lol, i accidentally mistyped an IP: 192.168.0.1117 instead of 192.168.0.117:doh: it took it some time to realize it cant connect to that.:rolleyes: ie, it sat tehre waiting to connect then said cannot connect to remote computer. heh. really, you THINK SO?

---

:badger:

[declassified]

I kept trying to remote-connect from vista to my old XP box and it never would work. I just gave up and one day it hit me - duh, the firewall...

[Mike Dimmick]

99.9% of all TCP clients will do the same thing. They will first attempt to decode the entry as an IP address using inet_addr. If that fails, getting a return value of INADDR_NONE, it'll then look up the name in DNS with gethostbyname. If that returns an address - which might happen if there's a wildcard in DNS, which there seems to be in .co.uk - then the client will try to connect to that address. If the address isn't actually contactable, it'll then wait for the TCP connect timeout - which is typically two minutes - before failing.

Stability. What an interesting concept. -- Chris Maunder

[uskorc]

Judging from the previous posts, the only one who could get a reply and a connection to that IP is Chuck Norris. And I think that Horatio Cane could also succeed. But that's just my opinion :)

[Vasudevan Deepak Kumar]

Anton Afanasyev wrote:

192.168.0.1117

RDP should have been bit smarter and alerted you "Did you mean 01.117"?

Vasudevan Deepak Kumar Personal Homepage Tech Gossips