asked on

cannot connect to terminal server

I am running small business server 2000 (also used as terminal server) and windows 2000 server, with a firewall vpn between both servers. I am able to connect with terminal server, using internal IP addressing from the workstations on the Windows server 2000 side, however when I try to connect from outside the vpn network, over the internet, using the server's outside IP address I receive the error,

"client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be to busy to accept new connections."

I have enabled port 3389 on the firewall.

Does anyone have any ideas?

Thanks,
Diane

sunray_2003

Diane,

Try checking this going to command prompt

netstat -a and you should see port 3389 listening

S

sunray_2003

You have already enabled the port ... But just check this to see if you get any idea

https://www.experts-exchange.com/questions/20645133/Win2K-Terminal-Server-over-Internet.html

S

dboyle53169

ASKER

It show port 3389 listening, I read that post, however I'm not sure exactly what it is I'm supposed to do.

Diane

svenkarlsen

please clarify: do you actually want to connect to the server from a connection via internet, NOT using VPN ?

Furthermore, do you have some sort of port-mapping on your firewall?
It cannot guess which server is supposed to receive the connection, - you must either have public IP-address on the terminal server or have the firewall configured to route the incoming connection to the appropriate address.

dboyle53169

ASKER

Using the internet Not over the VPN, Yes I have a port mapping on the firewall, I have a service setup for port 3389, mapped to the internal IP address of this server. I am using a SOHO3 Sonicwall. I've set these firewall's up many times and usually it's very easy and works perfectly. Possibly this has to do with some configuration in the server?

Diane

ASKER CERTIFIED SOLUTION

KingHollis

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

svenkarlsen

Just to check the route through the firewall: could you enable ICMP and port-map it to the server, - then ping it from outside ?

That would give a clou to where the problem is (i.e. at firewall or server)