Solved

Changed RDP port wont work win2008 - hyperv environment

Posted on 2011-09-04
3
469 Views
Last Modified: 2012-05-12
I have 4 Virtual servers running on a Hyper-v host.  All servers are win2008 ent edition x64.  There is a router and firewall at the front of the network and all server run static 192.168.n.n addresses. One server runs AD, DNS, DHCP.

On all servers i have static IP address and have changed each listening RDP port to 3385 (hyper-v host), 3386,3387,3388, (3389 / default port is reserved for the teminal services server).

The firewall is configured to port forward to the approriate port / Ip address and all works well except for the last server port 3388.  I cannot get that particular server to work on any port excpet the DEFAULT port 3389.

I have checked things like dual IPs wrong port forwarding.  I cant see anything that would prevent it from listening on the assigned 3388 port.  I have tesed the port from inside the firewall to eliminate the firewall as the issue.  As mentioned above it works on the default port 3389 ok.

Any help trying to figure out what could be stopping it from listening on my assigned port would be apprecaited.
0
Comment
Question by:martinmcginley
  • 2
3 Comments
 
LVL 15

Accepted Solution

by:
Perarduaadastra earned 500 total points
ID: 36480466
Hi

Try using port 3384 instead - if you still have the same problem  then it's likely to be a configuration or firewall issue rather than a peculiarity of the chosen port number.

Speaking of firewalls, have you checked whether the firewall on the affected VM is blocking the traffic? It's turned on by default, and the fact that 3389 works OK on that one but nothing else does would have me looking very carefully at its configuration before looking elsewhere, When you are configuring a number of similar and/or nearly identical computers it's very easy to think that you've done everything right on each of them and then discover that you've missed something out that you did on the others.

The fact that it's the last one in the sequence of non-standard RDP port numbers makes this more likely. Also, the fact that port 3389 still works on this VM indicates that it's not yet been told to listen on port 3388...
0
 

Author Closing Comment

by:martinmcginley
ID: 36481148
You were right. I had not turned off/modified the domain firewall block list on the server in question.  After I changed it all is fine. Thanks
0
 
LVL 15

Expert Comment

by:Perarduaadastra
ID: 36481359
Glad to help.
0

Featured Post

ScreenConnect 6.0 Free Trial

Explore all the enhancements in one game-changing release, ScreenConnect 6.0, based on partner feedback. New features include a redesigned UI, app configurations and chat acknowledgement to improve customer engagement!

Question has a verified solution.

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

by Nathan Brom/Bromy2004 Introduction There are numerous websites out there for any different type of program you can imagine.  Of those, you'll need to decide which ones are legitimate and aren't trying to steal your money or infect your comput…
This is a little timesaver I have been using for setting up Microsoft Small Business Server (SBS) in the simplest possible way. It may not be appropriate for every customer. However, when you get a situation where the person who owns the server is i…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

773 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