It is currently Fri Mar 29, 2024 12:03 am

All times are UTC - 7 hours [ DST ]

Recent News:



Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Tue May 20, 2014 2:20 pm 
Offline
Newbie
Newbie

Joined: Sun Oct 06, 2013 1:45 pm
Posts: 6
Thanks: 1
Thanked: 0 time in 0 post
Back in February 2014, Remote Desktop (RDT) would always connect to WHS after a short argument about the validity of the server security certificate. Now it just absolutely refuses to connect at all despite being offered the lowest security settings possible with Windows 7 Professional.

The current security certificate refers to http://my_name.homeserver.com but I am of course trying to connect using RDT to //HPStorage/ for which there is of course no such certificate as the box is sitting in front of me.

Rather than buy another certificate, which might work, is there any other way than with RDT to access this server?


Top
 Profile  
Thanks  

Attention Guest: Remove this ad by Registering with the MediaSmartServer.net Forums. It's Free!
PostPosted: Tue May 20, 2014 7:59 pm 
Offline
Moderator
Moderator
User avatar

Joined: Sat Oct 17, 2009 7:10 pm
Posts: 5157
Location: Georgia, USA
Thanks: 86
Thanked: 704 times in 682 posts
When using Remote Desktop to connect to your server on your own network just enter the name of the server without the slashes.

You do not have to purchase a new certificate it comes with WHS. As for connecting outside the network that may have more to do with where your connecting from then your server itself and if from work it may have to do with your companies IT Department blocking ports on their end. On your end if that's where the problem exists then it may have to do with your router not being configured properly by WHS for some reason but if you have reserved and internal IP number for your server through the router then you can also forward all the necessary ports the server will need to operate correctly and those ports are as follows:

80 - Used for HTTP Connections
443 - Used for HTTPS Connection
4125 - Used for Microsoft Remote Web Administration
3389 - Used for Remote Desktop Protocol (RDP) Terminal Server

I am not sure how your router is setup but if it can reserve IP numbers for your devices then I would reserve an IP number for the server so its always the same then I would forward all those ports to the server that way you do not have to rely on the routers universal plug and play setting and the server having to utilize it because it would be etched in stone if manually setup within the router.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8


Top
 Profile  
Thanks  
PostPosted: Wed May 21, 2014 2:20 am 
Offline
Newbie
Newbie

Joined: Sun Oct 06, 2013 1:45 pm
Posts: 6
Thanks: 1
Thanked: 0 time in 0 post
Thanks for the info, it sounds as though I may have brought this issue on myself if it turns out to be just a few extra slashes!
The internal LAN IP address of the server is fixed, and this has never been a problem, although port forwarding does give a few error messages from time to time. However, when I look at the router, everything for port forwarding looks fine.
I'll give it another try tonight and see how it goes, in the meantime, many thanks for your help.


Top
 Profile  
Thanks  
PostPosted: Wed May 21, 2014 2:57 pm 
Offline
Moderator
Moderator
User avatar

Joined: Sat Oct 17, 2009 7:10 pm
Posts: 5157
Location: Georgia, USA
Thanks: 86
Thanked: 704 times in 682 posts
Its not unusual for WHS to complain about port forwarding or even tell you that the router is not configured properly. Thing is you never really know until you actually test the server from outside your network. I look forward to reading your follow up post and I hope all goes well for you.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8


Top
 Profile  
Thanks  
The following user would like to thank Comp1962 for this post
philknowles
PostPosted: Fri May 23, 2014 6:50 am 
Offline
Newbie
Newbie

Joined: Sun Oct 06, 2013 1:45 pm
Posts: 6
Thanks: 1
Thanked: 0 time in 0 post
I now have a solution to this problem which I got from a Microsoft guy.
Following my discovery using sfc.exe that the file mstsc.exe was corrupted and not repairable, I installed the Microsoft utility Remote Desktop Manager (free software) which is designed for operating server farms but will also handle just one or two servers.
This works really well with no arguments about the validity of security certificates and looks just like the old Remote Desktop screen when connected.
I hope this might be of some use to you and anyone else who is looking at controlling multiple servers. This utility appears to be capable of handling a very large number of boxes.
Once again, many thanks for the information about port forwarding which should reduce the number of spurious alarms I receive.

Rgds, Phil Knowles


Top
 Profile  
Thanks  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 7 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group