Unable to browse to remote.domain.com from the external network only.

We are presently running Windows SBS 2011.  We are port forwaring 443 from an external IP, which we are performing 1to1 NAT, to the server on an internal IP.  Up until today it has worked great.

Today, we installed all the windows critical updates and we installed AVG anti-virus.

We are able to, from the LAN, browse to https://remote.domain.com and get the web login screen.  When we login from the Internet, we are getting the error from IE, The page you are looking for could not be found.

We checked DNS, it is resolving correctly.
We checked the port forward, it is working fine on 443 and 3389 for RDP.  RDP is working great.
We have gone to the application events and we do not see denials.

Thoughts?

Thank you ahead of time for your feedback!
shaw71Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

shaw71Author Commented:
Also, we disabled AVG, no change to external browsing to https://remote.domain.com
WORKS2011Managed IT, Cyber Security, BackupCommented:
IS TCP 987 open on the firewall?
shaw71Author Commented:
TCP 987 was opened with no affect.

I rebooted Windows SBS 2011 and the service was restored. Not sure what was happening as of yet, but it is working now.  Thank you for your input.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shaw71Author Commented:
After confirming with the firewall that all ports hadn't changed, and adding the additional TCP port 987, I have determined that it wasn't the firewall.

I rebooted the server and service was restored for outside remote.domain.com access.  Not sure what happened at this point. Waiting for the situation to duplicate in order to see if it happens again to specifically diagnose.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.