Server 2012, Routing & Remote Access and IIS

P00HB33R

Senior Member
Joined
Jul 15, 2010
Messages
708
Reaction score
29
Location
Eloff
Hi Guys

I am just about at my wits end.

I have a server running MS Server 2012 R2 with Routing & Remote Access. The RRAS service connects several offsite branches for inter-branch communication.

On the same server I have IIS running 3 websites, 2 are on port 80 and 1 on port 8079.

IIS works flawlessly. No downtime whatsoever. My problems starts with the RRAS (Remote Access) service.
It just stops randomly. And when I say randomly, some days it won't stop at all, other days it stops/restarts maybe 12 times.

Event Viewer gives me the following error on the RRAS Service:
- Services monitor has gone from HEALTHY state to UNHEALTHY state on 9/9/2016 at 2:05 PM on ******. The failure heuristic IDs for state change of Services are c0000001.

And this in the System Log:
-The Windows Management Instrumentation service terminated unexpectedly. It has done this 41 time(s).
-The Routing and Remote Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
-The Remote Access Connection Manager service terminated unexpectedly. It has done this 41 time(s).
-The IKE and AuthIP IPsec Keying Modules service terminated unexpectedly. It has done this 39 time(s).
-The Group Policy Client service terminated unexpectedly. It has done this 11 time(s).

Does anyone have a ideas/clues/suggestions? A case of beer/colddrinks might just make its way to you.

Any help would be greatly appreciated.
 
hmm could be a number of things, too little info.

is the NIC in that server OK? ive replaced a NIC on systems with similar issues and the issues didnt come back.

or ipv4 or ipv6 settings, somestimes ipv4 gets disabled.

or a role or service that is damaged after an update and needs to be reinstalled.

Seen power saving policies can cause this too.

or why not reinstall RRASS? or is too big a configuration to reset. or does it give the same result.
 
@access

Thanx for the reply. I have checked most of what you mentioned. Don't have access to the server itself thought as it is a hosted dedicated server, so rdp access mostly. I did notice something strange, when I stop the IIS service, the issue disappears. So now I am thinking there must be some port clash on the listener services. Does anyone know how to verify?
 
netstat -an | find /i "listening"

copy paste that to an elevated cmd prompt.

there is a TCP Port Sharing option in server Roles, Application Server. not sure if related.
 
C:\Users\Administrator>netstat -an | find /i "listening"
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8078 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8079 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8172 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8888 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49291 0.0.0.0:0 LISTENING
TCP 127.0.0.1:4001 0.0.0.0:0 LISTENING
TCP ***.***.***.***:139 0.0.0.0:0 LISTENING (Public IP masked for security)
TCP ***.***.***.***:139 0.0.0.0:0 LISTENING (VPN Server IP masked for security)
TCP ***.***.***.***:53831 0.0.0.0:0 LISTENING (VPN Server IP masked for security)
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1801 [::]:0 LISTENING
TCP [::]:2103 [::]:0 LISTENING
TCP [::]:2105 [::]:0 LISTENING
TCP [::]:2107 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:5985 [::]:0 LISTENING
TCP [::]:8078 [::]:0 LISTENING
TCP [::]:8079 [::]:0 LISTENING
TCP [::]:8172 [::]:0 LISTENING
TCP [::]:8888 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49157 [::]:0 LISTENING
TCP [::]:49291 [::]:0 LISTENING
 
there are other netstat commands that will show listening services, use " | more " to make it show by page.
 
Top
Sign up to the MyBroadband newsletter
X