pclos to XP pro over internet using rdesktop [solved]

[nerdful1]

 
I am kerfuddled, and google is no longer a friend, as I wore him out.

Project:

Running remote astronomy imaging camera with pclinuxos over internet.

Because of issues running the imaging software in Linux, it is running on XP pro for now. (Later I'll get the observatory imaging running on PCLOS using wine or virtualbox).

Over my local LAN, there is no problem running the remote xp computer either with either another XP machine, or PCLinuxOS with rdesktop.

I can pick a random laptop with PCLinuxOS, even WIFI, open a terminal, usually Yakuake, type rdesktop 192.168.1.107 -f and get a perfect full screen of the XP machine on the Linux laptop or box within seconds.
Operating the camera, telescope controls, all perfect as though I was at the XP machine.

Same perfection using a XP home machine to call the remote.
--
The above works on the local LAN side of my wifi router connected to cable modem.
--
Now I try to connect to the XP computer on its own DSL line.

Everyone says simply: rdesktop to the isp address of the remote machine.

If I try whatismyisp.com or several other methods, I get for example, 12.13.123.124, or the longer version: pool-12-13-123-124.ptldme.east.myfairpoint.net.

I try rdesktop -f 12.13.123.124, and combinations of all the above, and it does not compute.

Same if I try xp to xp machines.

The PCLinuxOS machine is still on the same router and cable modem as described in the beginning.

The XP machine is now on the Fairpoint DSL, with no router for now.

In some past checks, I saw that port 3389 was being used by xp.

What am I doing wrong? Please no alternatives like use ssh etc, I want this question answered.



Thanks

[kjpetrie]

The Wi-Fi router or the cable modem probably contains a firewall which is not forwarding the port, or the ISP might be blocking it, but that's less likely.

You need to consult the instructions for these devices to find out how to configure them to forward the data.

[nerdful1]

Then why does it work in the other cases?

As far as I know it was using port 3389 in the local instances.

Thanks.

[nerdful1]

FYI

It is a Linksys/cisco WRT54GL unmodified router.

Under 'applications and gaming' I have port 3389 enabled.

Not worried about security at this time, just want proof of performance.

I bought this particular router for future hacking, wnat to try thr Tomato stuff some day but at this point it just has the latest factory firmware.

Thanks

[kjpetrie]

Perhaps you need to explain the network better. You have a LAN which connects to the Internet through a cable modem, and the XP computer has a separate direct connection to the net? (check the Windows Firewall settings)

or you are trying to connect the XP computer to the net through the LAN and the cable modem? (check the router and modem settings)

[nerdful1]

"The PCLinuxOS machine is still on the same router and cable modem as described in the beginning.

The XP machine is now on the Fairpoint DSL, with no router for now."

What I meant by the above is the PCLinuxOS computer is on the Linksys/cisco WRT54GL unmodified router connected to a cable modem.

The XP machine is on a Fairpoint/verizon DSL modem with no router.

I am trying to use rdesktop which is on the PCLinuxOS machine and connected to the cable modem through the above router to operate  the XP machine by remote desktop, the XP machine being on the Fairpoint/Verizon modem on a phone line with DSL without a router:


PCLinuxOS computer running rdesktop===>Router===>Cable Modem===>Cable broadband service_______Internet_______DSL broadband service===>DSL Modem===>computer running XP pro.

Thanks

[kjpetrie]

And the network that works? The problem must be in the difference between them and will either be port blocking, a firewall, or misconfigured packet forwarding.

[TheGhost]

You seem proficient enough to know how to do the networking, so this is probably a dumb question, but: Is port forwarding configured in the router to direct your rdesktop request to the relevant computer?

If you try to access the computer using the router's WAN IP, you'll only get an answer from the router. You need to configure the router to direct the connection incoming over WAN to your computer.

Sorry if this is too obvious, but - I've been there - sometimes we overlook the simple stuff looking for the complex stuff.

[nerdful1]

Any answer is welcome, and I expect something really stupid on my part.

This router I bought to someday hack and play with firmware from Tomato and the like, but not right now.

It really has a sparse menu, can't reboot unless I crawl under to unplug, etc.

The only port stuff is under games and apps, udp/tp enable, and address of computers, which I checked again under your advice.

Nothing about transmit receive port settings.

Next step is to remove the router and run bareback to the cable modem. XP winders firewall is on, and the 2010 computer should be safe.

If that works, I may dig up an old wep only router I retired. I leave it open anyway.

And if that one works, maybe I'll try the firmware hacks in the wrt54gl.

Any further stupid answers welcome, making a checklist to be sure to not miss anything.

Thanks!

[nerdful1]

Tried with no routers this time, no help.

2010 computer connected directly to cable modem, firewall off.

XP connected directly to DSL modem, configured to accept remote connections.

Still get 'unable to connect' error with rdesktop.

[davexnet]

From within XP, you can open a CMD box and type ipconfig to get/confirm the IP address.
Can you ping that address from the PCLOS box ?

[nerdful1]

I was using whatismyisp.com, dslreports, or grc.com shields up to find the current address.

In each case that is what I confirmed first, as the dsl changes. the cable isp remains static.

I will use ipconfig too, just to be sure.

Thanks

[nerdful1]

So I'm still not getting anywhere.

Can I set up yet another computer and do packet sniffing or some traffic watching thing to see what these machines are sending to each other?

I'm not familiar with what we have in the repo to do this the best way.

Thanks

[pags]

Did you try davexnet's suggestion?

From within XP, you can open a CMD box and type ipconfig to get/confirm the IP address.
Can you ping that address from the PCLOS box ?

There could be a firewall in the modem itself...

"The PCLinuxOS machine is still on the same router and cable modem as described in the beginning.

The XP machine is now on the Fairpoint DSL, with no router for now."

What I meant by the above is the PCLinuxOS computer is on the Linksys/cisco WRT54GL unmodified router connected to a cable modem.

The XP machine is on a Fairpoint/verizon DSL modem with no router.

I am trying to use rdesktop which is on the PCLinuxOS machine and connected to the cable modem through the above router to operate  the XP machine by remote desktop, the XP machine being on the Fairpoint/Verizon modem on a phone line with DSL without a router:


PCLinuxOS computer running rdesktop===>Router===>Cable Modem===>Cable broadband service_______Internet_______DSL broadband service===>DSL Modem===>computer running XP pro.

Thanks

Do you have any documentation, or googled the make/model of this modem (particularly with regards to your ISP...they may configure something other than the defaults)...
Speaking of ISP, have you checked of they might be blocking ports?  You could try re-directing a non-standard port, to test that...

[nerdful1]

Turns out the Verizon DSL was not just a dumb modem like the cable modem.

westell/Verizon E90-610015-06 model 6100 with black and red menu.

Even though it only has one output, it has a full featured router menu in it.
I turned on port fowarding to 3389, and it works.

Really slow screen update, but it is on a minimal dsl.

Now to learn how to keep an XP box secure over rdesktop until I get the windows apps running in PCLinuxOS.

Thanks all!