Solved VPN Down Since Server Reboot
-
Are those ports blocked by your new ISP?
Ar you sure the system reboot didn't make any changes to the settings on the server?
-
@DustinB3403 said in VPN Down Since Server Reboot:
Are those ports blocked by your new ISP?
Ar you sure the system reboot didn't make any changes to the settings on the server?
Those ports were configured and working 100% until the reboot last night. I've never had a Windows Update make changes serious enough to disrupt VPN. Everything looks good but not sure what else to look for. Still combing both the firewall and our Windows Server that handles remote access. I have involved our new ISP but not sure when they will call.
-
RESOLVED...not sure why this was one of the last places to look but the actual ROUTING AND REMOTE ACCESS service was not running. Since it was set to Automatic, didn't think to check there yet as the actual SERVICE did show green. But can't trust that Automatic setting sometimes...
-
So windows updates did make a change, causing that service to not start.
It's always windows fault....
-
@garak0410 said in VPN Down Since Server Reboot:
RESOLVED...not sure why this was one of the last places to look but the actual ROUTING AND REMOTE ACCESS service was not running. Since it was set to Automatic, didn't think to check there yet as the actual SERVICE did show green. But can't trust that Automatic setting sometimes...
Plus when you have a VP who is wary of technology who finally trusted me to try to work away from home and then they can't get into VPN, you don't think straight sometimes...and yes, SOLO IT shop!
-
@DustinB3403 said in VPN Down Since Server Reboot:
So windows updates did make a change, causing that service to not start.
It's always windows fault....
Perhaps it would be good to review the event logs to see why the service failed before jumping to conclusions.
-
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 said in VPN Down Since Server Reboot:
So windows updates did make a change, causing that service to not start.
It's always windows fault....
Perhaps it would be good to review the event logs to see why the service failed before jumping to conclusions.
Assuming logging is enabled are we...
-
@DustinB3403 Isn't that one of the benefits of Windows?
-
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 Isn't that one of the benefits of Windows?
If it's turned on, sure.
Often it's not on.
-
@DustinB3403 said in VPN Down Since Server Reboot:
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 Isn't that one of the benefits of Windows?
If it's turned on, sure.
Often it's not on.
Event logs are always on for windows services.
-
@JaredBusch said in VPN Down Since Server Reboot:
@DustinB3403 said in VPN Down Since Server Reboot:
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 Isn't that one of the benefits of Windows?
If it's turned on, sure.
Often it's not on.
Event logs are always on for windows services.
But not always verbose logging to say why a service failed to start. Often it's "service failed to start, error #"
-
@DustinB3403 said in VPN Down Since Server Reboot:
@JaredBusch said in VPN Down Since Server Reboot:
@DustinB3403 said in VPN Down Since Server Reboot:
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 Isn't that one of the benefits of Windows?
If it's turned on, sure.
Often it's not on.
Event logs are always on for windows services.
But not always verbose logging to say why a service failed to start. Often it's "service failed to start, error #"
Very true. But that's not what you said. What you said implied that there was no logging.
-
@JaredBusch said in VPN Down Since Server Reboot:
@DustinB3403 said in VPN Down Since Server Reboot:
@JaredBusch said in VPN Down Since Server Reboot:
@DustinB3403 said in VPN Down Since Server Reboot:
@Danp said in VPN Down Since Server Reboot:
@DustinB3403 Isn't that one of the benefits of Windows?
If it's turned on, sure.
Often it's not on.
Event logs are always on for windows services.
But not always verbose logging to say why a service failed to start. Often it's "service failed to start, error #"
Very true. But that's not what you said. What you said implied that there was no logging.
My apologies, it's what I meant as I typed it.
-
@DustinB3403 said in VPN Down Since Server Reboot:
So windows updates did make a change, causing that service to not start.
It's always windows fault....
Windows is not doing well in the news today!
