USSC-IT
asked on
Server 2012 R2 NPS not starting
I am new to server 2012. I'm in a small environment and using my 2012 server as an integrated AD/DNS/DHCP/NPS server. I've successfully set up AD, DNS, and DHCP, and have NPS installed.
The error I get is:
Error 0x80072740: Only one usage of each socket address (protocol/Network address/port) is normally permitted.
I've found Microsoft posts that for server 2000/2003 a registry key existed to exclude those ports from the dynamic range. For server 2008 and beyond, that key has been sunsetted and is no longer used, in part because DNS dynamic ports have been shifted further up.
I've done a 'netsh int ipv4 show dynamicportrange udp' and found that the range is 49152-16384, which I'd expect. If you perform a netstat -ano | findstr 1812, nothing is using port 1812. (True also of 1813, 1645, and 1646).
I am at a loss as to where to go next. Any help is appreciated.
The error I get is:
Error 0x80072740: Only one usage of each socket address (protocol/Network address/port) is normally permitted.
I've found Microsoft posts that for server 2000/2003 a registry key existed to exclude those ports from the dynamic range. For server 2008 and beyond, that key has been sunsetted and is no longer used, in part because DNS dynamic ports have been shifted further up.
I've done a 'netsh int ipv4 show dynamicportrange udp' and found that the range is 49152-16384, which I'd expect. If you perform a netstat -ano | findstr 1812, nothing is using port 1812. (True also of 1813, 1645, and 1646).
I am at a loss as to where to go next. Any help is appreciated.
Do you have any security software installed on this box such as Symantec Endpoint, Websense Endpoint or any third party firewall software?
Something is using the port that the NPS service is trying to bind to and is unable to, netstat should tell you, I'd check the list manually.
netstat -an | more
Something is using the port that the NPS service is trying to bind to and is unable to, netstat should tell you, I'd check the list manually.
netstat -an | more
ASKER
The only thing that has been installed on this server is stock Windows Server 2012 R2 components.
I did do a raw netstat - there are no bindings showing for any of those ports on UDP (or on TCP for that matter). That's what is so confusing about the error.
I did do a raw netstat - there are no bindings showing for any of those ports on UDP (or on TCP for that matter). That's what is so confusing about the error.
Couple ideas:
1). If there are multiple network adaptors, disable all not in use then reboot.
2). Update network drivers
3). Uninstall TCP/IP (deselect from NIC properties, hit OK) and Reinstall (reselect in NIC properties and hit OK)
4). Are there any Group Policies applied to this box?
5). Does enabling/disabling windows firewall have any impact on this?
1). If there are multiple network adaptors, disable all not in use then reboot.
2). Update network drivers
3). Uninstall TCP/IP (deselect from NIC properties, hit OK) and Reinstall (reselect in NIC properties and hit OK)
4). Are there any Group Policies applied to this box?
5). Does enabling/disabling windows firewall have any impact on this?
ASKER
In response:
1. Only one adapter in use.
2. Network drivers appear to be up-to-date
Broadcom BCM5708C NetXtreme II GigE
v.7.4.23.2 from Microsoft
3. All other network services are working correctly, including DHCP, AD, and DNS, system in a production environment.
4. Same group policies that apply to the current Windows 2008 Server hosting RADIUS.
5. No effect. Firewall has the ports set for pass-through.
1. Only one adapter in use.
2. Network drivers appear to be up-to-date
Broadcom BCM5708C NetXtreme II GigE
v.7.4.23.2 from Microsoft
3. All other network services are working correctly, including DHCP, AD, and DNS, system in a production environment.
4. Same group policies that apply to the current Windows 2008 Server hosting RADIUS.
5. No effect. Firewall has the ports set for pass-through.
Download TCPView and double check the ports listed here. If netstat wasn't lying and nothing is bound to those ports then I would uninstall the NPS role and reinstall it.
http://technet.microsoft.com/en-us/library/cc732902.aspx
TCPView:
http://technet.microsoft.com/en-us/sysinternals/bb897437
http://technet.microsoft.com/en-us/library/cc732902.aspx
TCPView:
http://technet.microsoft.com/en-us/sysinternals/bb897437
ASKER
I will try TCPView and post my findings, thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
After confirming none of the stock RADIUS ports were being stepped on by another process, revisited the documentation and decided to explicitly tie the ports to a specific IPv4 adapter with each port, and start the process. Confirmed that the process was trying to step on itself by binding most likely to both the single live network IP and the localhost loopback address, as well as the IPv6 addresses.
ASKER