Solved

Terminal services - can't connect from outside lan, but can from inside

Posted on 2006-06-12
6
220 Views
Last Modified: 2010-04-18
For some reason, Terminal Services have stopped working properly on my Windows Server 2003 machine.  From inside the LAN, I can connect just fine...but nobody can get in remotely.  I've checked the licensing, local security policies, etc. and can't find anything that might be holding it up.  Everything seems fine, they just get a can't connect type message.

Kevin
0
Comment
Question by:Kevin Smith
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 13

Accepted Solution

by:
2hype earned 500 total points
ID: 16886569
Did you forward port 3389 on your firewall to your Terminal Server Computer.  Or do they connect to your office remotly via a VPN.  
0
 
LVL 7

Expert Comment

by:tolinrome
ID: 16886578
Kevin,
Was it working before or is this a new setup? Im assuming the problem is when a vpn client is trying to access network resources on the LAN from the internet. On your VPN server is the RRAS server properties on the general tab selected as a Remote Access Server? Do the clients have Dial-In access permissions checked on their userID properties? Are you allowing VPN Remote Access traffic in through the firewall?
0
 

Author Comment

by:Kevin Smith
ID: 16886676
Actually, using RDP.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 7

Expert Comment

by:tolinrome
ID: 16887169
If you want to use RDP to get inside your LAN, you must first use a user account that has vpn dial in access enabled. Once you connect with that, then you can open RDP insert the ip address or pcname and connect. Make sure the firewall is enabled for this access. Is it ISA server?
0
 

Author Comment

by:Kevin Smith
ID: 16887307
It was the firewall/port 3389 problem...forwarded it and all is well, thanks 2hype!

(and thanks tolinrome for the great effort...although your comments didn't specifically answer my question, they did help me learn a bit more about rdp).
0
 
LVL 7

Expert Comment

by:tolinrome
ID: 16887954
no problem...glad you learned something along the way.....
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question