32 replies
by diego Accepted solution
by rob miners Accepted solution
you configure routing and remote access?
Admin tools Routing and Remote Access.
by diego Accepted solution
by gechurch Accepted solution
by rob miners Accepted solution
Remote Access, Remote Desktop what is the difference? You are still trying to achieve the same thing. This is a file server.
I must admit that i didn't try to connect remotely to my FS before enabling Routing & Remote Access. My reading of setting up RAS enabled the internal and external connections to the FS.
Go to the Remote tab of the System Properties Control panel Select Remote Users. Is there a list of users?
Is the user account that you are using a member of Mobile Users, Remote Desktop Users?
The other thing to look at is your Firewall.
by diego Accepted solution
by ngruloos Accepted solution
Hi Diego,
this may be a license issue. To confirm this, please try using the console mode of your remote connection by running the command "mstsc /console".
If you can get it, then I would suggest that you upgrade your licensing, you can get more info at http://support.microsoft.com/kb/823313.
by gechurch Accepted solution
by jmirtc Accepted solution
I may be wrong but......
I am sure by default Win 2K3 will only accept 2 Remote connections
Check the "Users" Tab in "Task Manager" to ensure that there are no allocated but Disconnected Users
I had a Similar problem when an external user just disconnecting from the Server without Logging off first.
J
by ngruloos Accepted solution
Hello,
yes, a maximum of 2 users/sessions can use Terminal Server/Remote Desktop. If you want to extend this value, you need CALS as mentioned in my previous reply.
By using the console mode ("msdtc/console"), you won't have this restriction but you can only have 1 console session at a time.
Best regards,
Nico.
by michael Accepted solution
by diego Accepted solution
by michael Accepted solution
I spent 2 hours trying to get it to work on a server I was sure I had enabled it on only to find I had missed it out!
My other thought is to make sure your account is in the remote users group or you have got windows firewall enabled and haven't set the terminal services exception or your calling PCs firewall is snuffing out the return packets.
Try turning logging on in the firewall or use MS Network monitor to look to see if the packets are actually reaching the system.
by techpro34yrs. Accepted solution
Go to the control panel and open the firewall icon. Under exceptions make sure the File and printer sharing are checked and also make sure remote access is checked too.
This should open you up to remote access.
by ngruloos Accepted solution
by rob miners Accepted solution
by severanj Accepted solution
by enda_walsh Accepted solution
by philaaa13 Accepted solution
This may not help you directly since you say that other machines can still gain access to the server but it may help others who are reading this thread.
We have a server which had been accepting RD connections happily until it was restarted via a RD connection. The server refused to allow any RD connections until it was restarted at its own console.
by dan.elder Accepted solution
by rainbow_networks Accepted solution
We had the same problem on 2 servers and your advice solved it.
Thanks.
by shravankoolin Accepted solution
go to
start-Programs-Administaror tools-service-IPsec(stop service,make ths service as manulal bcoz default itis automatic and start the service and reboot the server.)
by sbkurid Accepted solution
Me too facing the same problem but my server is citrix server running on windows 2003 standard edition....
any solution pls..
thanks!!!!
by daryl.connell Accepted solution
I was having the same issue. I disabled and re enabled remote access, removed all of the current users with remote access and re added them and I was able to connect with out a problem.
I hope that this helps,
D
by paul Accepted solution
by blue_nike2903 Accepted solution
I think better use Teamviewer.simple. Make you can control and remote your computer from anywhere anytime.
Here if you want tutorial step by step with picture how to remote pc use Teamviewer
by tdilisio Accepted solution
by akpeac Accepted solution
by slipdipidis1975 Accepted solution
The issue is with one of two things... most likely the latter. Either a security update that affects the files currently running in the process stack has been changed which means the server needs to be restarted OR...
Most likely, the port used to remote into your server has been changed... it's very common. Instead of 3389 for RDC, someone changed it and forgot. You can always load the registry hive for that server remotely (assuming you cannot easily access the console itself) and go to HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp
You will see what port is being used to remote in. To connect to that port using Remote Desktop, simply add a colon followed by the new port number (no spaces). it will look something like mysvr1:3390
by adam_ski Accepted solution
by bialy_mis Accepted solution
did the usual after applying patches and rebooted remotely
server came back as expected - but could not get it to talk to me via remote desktop
since the server is few meters away I rebooted the server from server console - works ok - happened 2 times already must be a security issue
by calneal12 Accepted solution
There is another solution that I had to try myself (since I could not find any other help from any other websites) but this worked for me:
- Start Menu -> Control Panel -> Administrative Tools -> Services
- Enable "Terminal Services" Service
After this, I was able to successfully connect to the server via RDC.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending