I've been encountering issues with the communication to some of my distributions points worldwide. The server is live but is unable to receive any packages.

I troubleshooted the issue with our network group and it seems that the servers are trying to send the data through the 1027 port

Now for the kicker: These are all 2008 R2 servers and port 1027 is part of the WMI range for server 2003. The port range for 2008 starts at 49152.

the issue in itself is easy enough to fix as you can see below:

netsh int ipv4 show dynamic tcp (this give you the current range)

netsh int ipv4 set dynamic tcp start=49152 num=**** (this allows you to set the beginning of the range to what you want and the # of ports available)

this requires a reboot to be effective.

My question is, why is the default port range changing without an input from anyone?

these ports are valid for windows 2003, for 2008 the wmi default port range starts at 49152

my question was as to why the default port range changed on some servers without any input from anyone

• Edited by Carl_Meilleur Friday, November 21, 2014 12:06 PM additional info

Hi Carl,

As you point out, in Windows Server 2008 and later versions, and in Windows Vista and later versions, the default dynamic port range changed to the following range:

• Start port: 49152
• End port: 65535

After my research, I found a relevant KB we can reference:

The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008

http://support.microsoft.com/kb/9298

This is information i already referenced in my initial posting, my question was what could cause the default port range to change on a win 2008 r2 server without any user input the command that i also referenced in my initial post

Hi,

It's stange. I recommend you use Process Monitor to find the root cause.

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.

Process Monitor v3.1

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

the issue is that i only find out when the server reboots and that when i try to force a hardware inventory through SCCM's right click tool it fails to communicate with the server

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.