Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Terminal Service over Internet
- Thread starter Bickyz
- Start date
yes:
for the technical details, firewall etc, dont ask me... i'm still looking...
good luck
for the technical details, firewall etc, dont ask me... i'm still looking...
good luck
It's absolutely possible and done every day all over the world. It's how I am able to monitor and administer servers that are hundreds of miles away, and do it from the comfort of my comfy chair.
First, you need to check with your IT department and make sure that this is acceptable and that your user profile allows for remote connections. Remember that some companies have policies regarding who is allowed to make remote connections.
Your IT department will also be able to advise you with regard to what IP address you need to use for your client connection, and if they have a non-standard listening port (i.e., something other than port 3389) configured for the Terminal Server itself.
Once you've got that info, if you need more help, I'll be happy to share what I know.
First, you need to check with your IT department and make sure that this is acceptable and that your user profile allows for remote connections. Remember that some companies have policies regarding who is allowed to make remote connections.
Your IT department will also be able to advise you with regard to what IP address you need to use for your client connection, and if they have a non-standard listening port (i.e., something other than port 3389) configured for the Terminal Server itself.
Once you've got that info, if you need more help, I'll be happy to share what I know.
- Thread starter
- #4
i myself has a small 3 computer's network at my home. 1 win2k server and 2 w2k prof pc.
Now i wanna access my server frm my friends house who has win2k pro pc, i want it to be accessed using terminal service. i hav installed terminal server in my home server and terminal client in my friends computer. Both end has broadband connection. Now what shall i do?
Now i wanna access my server frm my friends house who has win2k pro pc, i want it to be accessed using terminal service. i hav installed terminal server in my home server and terminal client in my friends computer. Both end has broadband connection. Now what shall i do?
First, know what your IP address is for your connection at home. (i.e., 66.122.222.222).
Second, know what internal IP address belongs to the machine you have assigned as your Terminal Server at home. (i.e., 192.168.1.259). Note that you can't just allow DHCP auto assignment for the addresses.
Third, create a pinhole or access point through your router/firewall for port 3389 (which is the standard listening port on the Terminal Server.)
You should be good to go from here.
Second, know what internal IP address belongs to the machine you have assigned as your Terminal Server at home. (i.e., 192.168.1.259). Note that you can't just allow DHCP auto assignment for the addresses.
Third, create a pinhole or access point through your router/firewall for port 3389 (which is the standard listening port on the Terminal Server.)
You should be good to go from here.
do you have to install the tsweb client on the tServer itself, or can you have a web server that relays to the TServer...
cos i tried to implement over the web, opening up the port 3389 on my firewal, and by redirecting...
i connected to the web client on my IIS machine, but the activeX component returns an error saying target machine not found....
can someone detail step by step what must be really easy to do but that i cant figure out all the same....
cos i tried to implement over the web, opening up the port 3389 on my firewal, and by redirecting...
i connected to the web client on my IIS machine, but the activeX component returns an error saying target machine not found....
can someone detail step by step what must be really easy to do but that i cant figure out all the same....
The web client simply installs software on your client computer which uses RDP to communicate with the TServer. For the "client computer" you need to put in the public IP address or DNS name of the TServer. Using the private address or NetBios name won't work since you're communicating directly with it via the Internet, not through the web server.
- Thread starter
- #9
Is there any way i can use the TSWeb virtual application on my IIS.... visible with firewall and port redirection...
then redirect the client to a TSE on the internal network...
or should I install IIS on the TSE (we have 2), set up each to respond on a different port then give out our public IP with the port, in order to let ppl connect.....
i dont have ISA, its a adsl modem router with firewall possibilities.....
cos our vpn keeps crashing and the distant users can not connect . . . .
heyulp ! ! ! !
then redirect the client to a TSE on the internal network...
or should I install IIS on the TSE (we have 2), set up each to respond on a different port then give out our public IP with the port, in order to let ppl connect.....
i dont have ISA, its a adsl modem router with firewall possibilities.....
cos our vpn keeps crashing and the distant users can not connect . . . .
heyulp ! ! ! !
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
