Safe Connect » Troubleshooting
- Make sure the computer’s date is correct. If the date is not correct a number of detection issues can be created.
- Clear browser cache.
- Check network connectivity.
- Check personal/Windows firewall(s).
- If you are experiencing difficulty with authentication, verify that you are using the correct e-campus id and mail.uri.edu password.
- If you do not know your e-campus id, go to http://web.uri.edu/ecampus/.
- For further help, contact the helpdesk.
If you are having problems authenticating, make sure you are using the correct login credentials: your eCampus username and mail.uri.edu password.
- If you do not know your eCampus username, please see http://web.uri.edu/ecampus/.
- If you are still having trouble, call the Help Desk (874-HELP). If you do not have an eCampus username, you can request a Guest Access Account
|This article is for experienced users ONLY. Do not attempt the following if you are unfamiliar with the material. If in doubt, please contact the Help Desk at 874-HELP.|
The Safe Connect Client requires administrator privileges to run. If you uninstalled Safe Connect without Administrator privileges, uninstall it, then reinstall by right clicking on ServiceInstaller.exe and selecting Run as Administrator.
In order for Safe Connect to recognize that you have the Safe Connect client installed, the Safe Connect client must be allowed access to the internet. If you have downloaded and installed the Safe Connect client, but you are still being prompted to download the client, then the Client is unable to communicate with the Safe Connect enforcer. In most cases, this is caused by a firewall program blocking communication between the master and the enforcer.
If after installing Safe Connect, you are prompted to allow scManager.sys or scClient.exe access to the internet, select allow. Not allowing Safe Connect to access the internet will cause the Safe Connect enforcer to think that you have not installed Safe Connect, and as a result, not allow you access to the internet.
In a very small number of cases, a server program running on your computer could prevent Safe Connect from communicating.
If you are running a web server, or any server that might bind to tcp port 8080 on localhost, try stopping that program then restarting the Safe Connct client. If after stopping the program, you are able to get past the Safe Connect download page, you should find a way to stop/reconfigure the program, or call the Help Desk (874-4357) to work towards a solution.
To verify that there is another program bound to port 8080:
- stop the Safe Connect client
- Using the Task Manager, verify that the Safe Connect client is no longer running.
- open a Windows Command Prompt. Do this by holding the Windows key down and Pressing R and then entering “CMD” into the box. In the command prompt ype
netstat -an. If there is a line like
TCP 127.0.0.1:8080 0.0.0.0 LISTENING, then another program is preventing Safe Connect from communicating. If you’re not sure which program, call the Help Desk (874-4357).