This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Connection Refused
Lomar Lilly edited this page May 17, 2016
·
7 revisions
####To avoid problems finding and downloading newsgroups, port 119 needs to be accessible. If this port is not accessible you'll see the follow error message:
Connection Refused Error on Windows | Connection Refused Error on Unix |
---|---|
####To fix this issue, you need to open port 119 and allow connection
Open port on windows | |
---|---|
1. Go to Control Panel. Click the System and Security link and then click Windows Firewall.You see the main Windows Firewall control window. |
screenshot |
2. On the left, click the Advanced Settings link. You see the Windows Firewall sanctum sanctorum |
screenshot |
3. On the left, click Inbound Rules. Then, on the right, under Actions, click the New Rule link. Windows Firewall shows you the New Inbound Rule Wizard. |
screenshot |
4. Select the option marked Port and click Next. The wizard asks you to specify which ports |
screenshot |
5. In the Specific Local Ports box, type 119 and then click Next. |
screenshot |
6. Choose Allow the Connection and click Next. The New Inbound Rule Wizard wants to know whether it should apply this rule if you’re connected to a domain network, a private network, or a public network. The safest option is to make it only open on your home network. |
screenshot |
7. Check the boxes for Private or any other desired network type, and then click Next. The wizard asks that you give the rule a name and, optionally, a description. |
screenshot |
8. Type a name (usually the name of whatever program required the opening). Click Finish. Your new rule appears in the Inbound Rules list. It takes effect immediately. |
screenshot |
- Home
- Download and Install
- User Guide
- MSc Report Abstract
- Links
- The Open Source Libraries Used
- System Requirements
- Known Issues
- Developer notes