Here’s a simple situation I ran into today. I’ve been troubleshooting an intermittent problem with a Windows 2008 R2 server for a few weeks now. I opened a Microsoft support ticket and the problem was believed to be due to port exhaustion in the dynamic port range. I confirmed the max ports were at 16,184 which was the default at the command prompt.

netsh int ipv4 show dynamicport tcp
netsh int ipv4 show dynamicport udp

I then needed a quick way to test this so I came up with this simple script. I had to use the CLI utility netstat because this server does not have Powershell v4 on it else I would have used Get-NetTCPConnection.

I figured I’d share to save someone a little bit of time figuring out how to get the TCP/UDP connection count on a remote server.


Ready to stop reading and start learning about PowerShell, DSC, Windows Server, Sharepoint, IIS and dozens of other categories? If so, check out the hundreds of absolutely no-PowerPoint, technical demo screencasts available on the new, IT e-learning platform TechSnips. Click here for a 7-day free trial to see what it's all about!

%d bloggers like this: