It does work when I use the relay through server setting.

I also just installed the pro version on the two clients and a pro server, and tested, and got the same results.
(I have reverted to the free version)

What I don't get is why the relay method works, and the direct method does not.

If the server was running from the same IP as the vista machine, would relay not fix the problem?

If you guys have any debug executables you want me to try, I would be willing to run those as well.

(If not for this issue, I think NeoRouter would replace Hamachi for me. LogMeIn has completely dropped the ball with Hamachi now, and I have been searching for a new solution, and NeoRouter looks like the guy. I'm very curious to see where NeoRouter will be when you guys are ready for making the Pro version commecial)

Thanks.

Hi mugendai,

We are still investigating it.

Can you tell us what model of router do you use in front of the WinXp that has the issue?

Thanks,
KevinZ - NeoRouter team

KevinZ,

Have you guys gotten any other ideas on this?
Is there anything I can do to help?

Thanks.

Hi mugendai,

We are still investigating it. It looks like an issue related to the terminal service.

So far we know it may happen when one RD to a WinXp machine logging in with the user, with which one installs NeoRouter.

Some tips:
1.Set NR client to use Relay mode instead of P2P
2.Use RD logging with other Windows user accounts
3.Log off from the local computer before doing RD over NR

We will get back to you when we figure it out. If someone have a similar issue or new information, please post here.

Thanks,
KevinZ - NeoRouter team

Kevinz,

I just wanted to let you know that the latest update: 0.9.12 fixed my problem with Remote Desktop.

You guys are really doing an awesome job on this product.

Thanks again.

(P.S. really hoping for that android version now.. (^_^) )

This is happening to me as well on NeoRouter Free 1.3.0.2526 [1] on only one machine. I have a single computer that I'm trying to RDP into on the other side of the world and two computers on my local network, both on the same windows and neorouter versions. The desktop exhibits this behavior, the laptop does not.

FWIW, the desktop worked fine before upgrading to the latest NeoRouter. I wonder if something regressed in the latest update?