SBS 2008 RWW suddenly not connecting without error
My RWW has been working fine . Lately I have been experiencing a situation where :
When a user tries to connect . remote.mycompany.com
I get waiting for remote.mycompany.com
this just goes on without a timeout or other error .
The only thing in logs is about certificates which expired 2 years ago .
I am at a loss as to what may be causing this and since this site hosts many remote users I am reluctant to just go in and poke around without guidance.
Has anybody experienced this ?
The problem goes away with a server reboot but this is not a good fix as you can imagine .
Help ? Anyone ?
When a user tries to connect . remote.mycompany.com
I get waiting for remote.mycompany.com
this just goes on without a timeout or other error .
The only thing in logs is about certificates which expired 2 years ago .
I am at a loss as to what may be causing this and since this site hosts many remote users I am reluctant to just go in and poke around without guidance.
Has anybody experienced this ?
The problem goes away with a server reboot but this is not a good fix as you can imagine .
Help ? Anyone ?
Firstly you need to take care of the certificate. If it a self signed cert opposed to a trusted cert then you can renew by doing the following:
Open the SBS Console > Network Tab> Connectivity sub tab.
Run the Fix My Network wizard
The actual timeout issue is probably due to either the IIS Service as suggested by JardaCZ or the World Wide Web Publishing service. Check the event logs for any clues.
If restarting the two services fails to resolve the problem then check the Application Pools in IIS manager to see if they are started.
Open the SBS Console > Network Tab> Connectivity sub tab.
Run the Fix My Network wizard
The actual timeout issue is probably due to either the IIS Service as suggested by JardaCZ or the World Wide Web Publishing service. Check the event logs for any clues.
If restarting the two services fails to resolve the problem then check the Application Pools in IIS manager to see if they are started.
ASKER
It is inaccessible locally or externally .
Some further info . It seems exchange stopped functioning too at the same time.
a reboot again brought it back for now.
I want to run the fix my network wizard but since I am supporting remotely I am concerned about losing connectivity if that goes wrong .
Should that be a concern ?
Some further info . It seems exchange stopped functioning too at the same time.
a reboot again brought it back for now.
I want to run the fix my network wizard but since I am supporting remotely I am concerned about losing connectivity if that goes wrong .
Should that be a concern ?
You can run the wizard. It will just scan he configuration to identify any warnings / errors.
It's when you proceed to resolve the errors that you may lose connection momentarily.
Run the fix my network wizard and post a screen shot before clicking fix if you're unsure.
In addition run the Best practice analyser to find further errors.
The event log is still your best bet at the moment.
It's when you proceed to resolve the errors that you may lose connection momentarily.
Run the fix my network wizard and post a screen shot before clicking fix if you're unsure.
In addition run the Best practice analyser to find further errors.
The event log is still your best bet at the moment.
You can set-up router to forward (NAT) 3389 to servers IP and use RDP access instead of RWW. Then run fix my network wizard.
Jarda
Jarda
ASKER
hmm . I have sonicwall . Can you explain how to do this ?
ASKER
David,
Will do ,
The event log seems useless . As I said its warning about a certificate that expired 2 years ago as the only even surrounding this issue .
It is weird that it is kicking up that one though .
Thats the only coincidence.
Will do ,
The event log seems useless . As I said its warning about a certificate that expired 2 years ago as the only even surrounding this issue .
It is weird that it is kicking up that one though .
Thats the only coincidence.
Andre, you should ask your router administrator to do this.
Port forwarding from WAN to LAN, port 3389.
Jarda
Port forwarding from WAN to LAN, port 3389.
Jarda
ASKER
ok I plan on working on this tonite and will let you know .
ASKER
David ,
Attached is the fix my wizard screen shot
Attached is the fix my wizard screen shot
Hello,
Select only the root certificate tick box and continue the wizard. It will attempt to renew it. It should succeed.
Then check the event log for any additional cert expiry warnings.
After that run the Best Practice Analyser and see if it shows anything.
Select only the root certificate tick box and continue the wizard. It will attempt to renew it. It should succeed.
Then check the event log for any additional cert expiry warnings.
After that run the Best Practice Analyser and see if it shows anything.
ASKER
David ,
Did what you said (Thanks!!) and it said fixed and gave the attached Certs events :
I also ran fix my network again and the cert error did not recurr .
It also threw event Id 64 for at least 3 thumbprints .
In addition and what is now most interesting especially since I had also experienced exchange outage when the remote access went out is I have and still have the attached event( Exchange-TLS )12016 error now.
Could that have stopped exchange ?
I am VERY nervous about cert work as I here its a pain to do .
I would like to get to the bottom of this as they rely heavily on Email and remote access.
Certs-Events
exchange-tls.txt
Did what you said (Thanks!!) and it said fixed and gave the attached Certs events :
I also ran fix my network again and the cert error did not recurr .
It also threw event Id 64 for at least 3 thumbprints .
In addition and what is now most interesting especially since I had also experienced exchange outage when the remote access went out is I have and still have the attached event( Exchange-TLS )12016 error now.
Could that have stopped exchange ?
I am VERY nervous about cert work as I here its a pain to do .
I would like to get to the bottom of this as they rely heavily on Email and remote access.
Certs-Events
exchange-tls.txt
Hi Andre,
Can you confirm that the Active Directory Certificate Services is started?
Do you get any other certificate errors when running the FMNW?
Can you also download and run the SBS Best Practice Analyser and run a scan. Let us know the results.
Can you confirm that the Active Directory Certificate Services is started?
Do you get any other certificate errors when running the FMNW?
Can you also download and run the SBS Best Practice Analyser and run a scan. Let us know the results.
ASKER
David,
Active Directory Cert Services are running
I had 3 event 64 errors when running the FMNW
The Best Practice are attached .
The only other Certificate related error is attached .
could this be related to the problem I am having ?
If so I dont think the FMNW has corrected it .
note :remote.company.com mentioned in the exchange cert is how users access RWW .
Thanks so much for your continued help !
Best-Pract-A.png
Best-Pract-B.png
Exchange-Cert-Error-.png
Active Directory Cert Services are running
I had 3 event 64 errors when running the FMNW
The Best Practice are attached .
The only other Certificate related error is attached .
could this be related to the problem I am having ?
If so I dont think the FMNW has corrected it .
note :remote.company.com mentioned in the exchange cert is how users access RWW .
Thanks so much for your continued help !
Best-Pract-A.png
Best-Pract-B.png
Exchange-Cert-Error-.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's not connecting only from outside or you cannot login internally too?
You can try to restart some services instead of server, it will give you a clue where to find the error.
I'd try to restart IIS.
Let us know.
Jarda