tsweb not working on SBS 2003

[spudnuts]

I'm running SBS 2003 and i'm trying to remote connect using tsweb but keep getting the following error:

VBSCRIPT: Remote Desktop Disconnected

The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator.

I've gone onto the server and went directly to the site and it works fine. The logon page comes up, I type in the server name (FQDN) and click "Connect" and it works.

If I try it from another computer, I get the logon screen, type in the server name (FQDN) and when I click "Connect" I get a blank screen with a border around it and after about 30 seconds the above error comes up.

Any ideas?
Thanks

Information Assurance,CCNP,CST

 

[58sniper]

Is this from outside your environment? If so, is port 3389 open on your firewall?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP

 

[spudnuts]

Yes, outside. Works inside but not outside.

Not sure about port 3389, i'll have to check ISA and see but I was assuming that since I configured remote access that it would have done that for me.

Network Engineer, CCNP,CST

 

[spudnuts]

I'm not sure if I did this right but obviously not because it's not working.

I went into ISA
Created a Listener for port HTTP port 3389
Then I created a web server publishing rule, allowing internal and external for everyone using the above listener.

Hasn't changed anything, same result.

I havn't really messed with ISA before so i'm not sure if I set it up right. I set up a server with SBS 2003 and my website is being published great (although there isn't much on it but it is public). I'm just having problems with terminal services and email. My email is only coming in, nothing going out.

Thanks for the response.

Network Engineer, CCNP,CST

 

[ShackDaddy]

On the mail issue, try and telnet to a remote mailserver from your server, using port 25. If you can't reach anything, your ISP may have blocked outbound port 25 access. This is common, and you usually just have to call them up and ask them to remove the block.

On the TSWeb thing, are you directing 3389 traffic to your server? I don't think you need to be creating an HTTP port. You need inbound 3389 traffic forwarded to your server. There's no HTTP involvement at that stage. So you need two things: 1) ability to hit your server with HTTP and 2) ability to hit your server with 3389. Don't apply any HTTP fixup on the 3389 traffic. They should be separate rules, and I think you already had an HTTP rule to start with.

ShackDaddy
Shackelford Consulting

 

[ShackDaddy]

BTW, I don't use ISA much at all, so my terms may not translate directly to the ISA environment.

ShackDaddy
Shackelford Consulting

 

[spudnuts]

I was able to telnet to my server on port 25 with no problems.

On the other issue, I shut down ISA to see if I can do it without ISA and nothing worked. Thought that if I shut down the firewall and alloed everything then it should work but I think that ISA is so integrated in SBS that nothing worked when I did that.

I think i'll open the firewall for everything and then try, that way I can narrow down what the problem is.

Network Engineer, CCNP,CST

 

[ShackDaddy]

Telneting TO your server only tests inbound mail. You need to test OUTBOUND telnet to port 25 on REMOTE mailservers to figure out what your outbound mail issue is.

ShackDaddy
Shackelford Consulting