TSAC error out behind NAT setup

[dimitric]

Greetings,

I have a home AD setup with a netgear rt314 router. It has port 3389 open and I can connect to my Terminal Services server (192.168.0.99) through NT on a myname.dyndns.org account that my router sets up. I can use the client software fine, but if I try to use the TSAC web client, when I hit 'connect' I get the window frame but I get a vbscript error. I've debugged it and it either errors with error code 520 if I use netbios name or error code 516 when using the IP address.

I've looked these up, 520 means can't find computer ..so I use IP address and get 516 which means can't create socket. I've tried using FQDN and all that jazz..but no luck.

I'm thinking , can you even use TSAC behind NAT with port forwarding??

 

[peterve]

can you use the TS client software from a remote location, using the fqdn yourname.dyndns.org ?

Peter Van Eeckhoutte
peter.ve@pandora.be

 

[dmose]

yep I can run the client from anywhere in the world...as port 3389 is open on my router. Thats's what boggles me??

 

[peterve]

hmmm
did you modify the sample website that is included in the TSAC package from microsoft ?

just to make sure :
on the remote computer,
can you create a hosts file,
include a name (any name, for example : TSSERVER) and map it to the current IP address of your server
then try to connect to TSSERVER in your tsac web client and see what happens (just to make sure that your web client is working well)
Peter Van Eeckhoutte
peter.ve@pandora.be

 

[dmose]

Hey Peter,

Yeah I made a mapping in my host file and I still get the same error (520).

The web client is working, as I can use it to connect to other terminal servers.

The only thing I modifed in the sample pages was the error codes. I used code provided by MS (this was only after I initally tried it out and it didn't work)

I don't think its the webcode..I'm still baffled. Thanks for your help/interest btw. Any other sugguestions?

-Dimitri

 

[dmose]

Oh and I think I mentioned it before, but I can use the TSAC fine when on a local intranet machine (192.168.0.xxx subnet.) The only problems are when I try to connect via the

http://www through

my router.

 

[peterve]

is your router doing NAT ? (I've seen the TSAC client acting weird before when using NAT) Peter Van Eeckhoutte
peter.ve@pandora.be

Did this post help ? Click below to let me know ;-)

 

[dmose]

Yep its doing NAT indeed. I'm routing from a public, dhcp assigned xDSL ip to my private ip range of 192.168.xxx.xxx.

I guess that's the problem ..I'd probably have to put the server on a DMZ which is a bad idea. I guess I'll stick to using the client software.

-dimitri

 

[peterve]

putting it into a DMZ is not necessarily a bad idea
as long as you install a firewall which can handle anti-spoofing, it should work fine... Peter Van Eeckhoutte
peter.ve@pandora.be

Did this post help ? Click below to let me know ;-)