| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| troubleshooting:connectionui [2007/06/01 21:01] – texasfett | troubleshooting:connectionui [2008/12/22 13:52] – Add Windows HOSTS file checks to the list xuesheng |
|---|
| Although every person's setup will be different, it's generally a good idea to start with the basics and eliminate the obvious issues in a methodical manner. Try stepping thru each of the following to identify the problem on your system: | Although every person's setup will be different, it's generally a good idea to start with the basics and eliminate the obvious issues in a methodical manner. Try stepping thru each of the following to identify the problem on your system: |
| |
| * Make sure POPFile is really running. Check the task manager (Ctrl, Alt, Del) and look for an instance of either popfilef.exe, popfileif.exe, popfileb.exe or popfileib.exe. If you do not find one, then POPFile is not running. Start POPFile and try connecting to the UI after it starts up (allow a minute or so for it to load the corpus and other housekeeping). | * Make sure POPFile is really running. On Windows systems check the Task Manager (Ctrl, Alt, Del) and look for an instance of ''popfilef.exe'', ''popfileif.exe'', ''popfileb.exe'' or ''popfileib.exe''. If you do not find any of these programs then POPFile is not running. Start POPFile and try connecting to the UI after it starts up (allow a minute or so for it to load the corpus and other housekeeping). |
| |
| * Confirm you are using the correct link to access the UI. The correct link for those who have not changed the User Interface Web Port from the default of 8080 is http://127.0.0.1:8080/ (Note that the %%http://%% portion is not optional, you must include it ). | * Confirm you are using the correct link to access the UI. The correct link for those who have not changed the User Interface Web Port from the default of 8080 is http://localhost:8080/ (Note that the %%http://%% portion is not optional, you must include it ). |
| |
| * If the above link does not work, try the following alternative link http://localhost:8080/. | * If the above link does not work, try the following alternative link http://127.0.0.1:8080/. If this link works but http://localhost:8080/ does not then there may be a problem with the //hosts// file. The //hosts// file should include a line like this<code>127.0.0.1 localhost</code> |
| | * Note that on Windows systems you can use **either** space **or** tab characters to create the gap between **127.0.0.1** and **localhost** (do __**not**__ use a mixture of spaces and tabs). The default locations of the //hosts// file on Windows are:<code> |
| | Windows Vista = C:\WINDOWS\SYSTEM32\DRIVERS\ETC |
| | Windows XP = C:\WINDOWS\SYSTEM32\DRIVERS\ETC |
| | Windows 2000 = C:\WINNT\SYSTEM32\DRIVERS\ETC |
| | Windows 98/ME = C:\WINDOWS |
| | </code> |
| | * As an alternative to editing the //hosts// file, access the POPFile UI then go to the ADVANCED page. There is a long column of POPFile parameters on that page. Find the one labelled "bayes_localhostname" and enter 127.0.0.1 into the box (the default setting is an empty box). Click the "Update" button at the bottom of that column to save this change. Now shutdown POPFile and re-start it - the system tray icon will now use http://127.0.0.1:8080 to access the UI. |
| |
| * Check for other programs using port 8080. Shutdown POPFile, then open a DOS box and issue the netstat command, e.g., <code> | * Check for other programs using port 8080. Shutdown POPFile, then open a DOS box and issue the netstat command, e.g., <code> |
| * Obtain [[http://www.lavasoftusa.com/| Ad-aware from Lavasoft]] and/or [[http://security.kolla.de/| Spybot Search & Destroy]] and run it to remove all spyware from your machine. Some spyware causes issues with your TCP/IP stack and may make it impossible to connect to POPFile. | * Obtain [[http://www.lavasoftusa.com/| Ad-aware from Lavasoft]] and/or [[http://security.kolla.de/| Spybot Search & Destroy]] and run it to remove all spyware from your machine. Some spyware causes issues with your TCP/IP stack and may make it impossible to connect to POPFile. |
| |
| * Confirm your TCP/IP stack is operating correctly. As a last resort try the LSP Fix utility, it is a free utility to repair damaged Winsock settings: http://www.cexx.org/lspfix.htm. //Windows XP SP2 is supposed to repair LSP damage automatically, this utility was written before XP SP2. It appears safe to use on SP2.// | * Confirm your TCP/IP stack is operating correctly. [[ http://www.cexx.org/lspfix.htm | LSP Fix utility]], it is a free utility to repair damaged Winsock settings. //Windows XP SP2 is supposed to repair LSP damage automatically, this utility was written before XP SP2. It appears safe to use on SP2.// |
| |
| * If LSPFix doesn't help, [[http://www.spychecker.com/program/winsockxpfix.html | WinSock XP Fix]] might (Windows XP only). //This method has not been tested by POPFile developers.// If you are using XP SP2 running this at the command prompt, is supposed to do same thing:<code>netsh winsock reset</code> | * If LSPFix doesn't help, [[http://www.spychecker.com/program/winsockxpfix.html | WinSock XP Fix]] might (Windows XP only). //This method has not been tested by POPFile developers.// If you are using XP SP2 running this at the command prompt, is supposed to do same thing:<code>netsh winsock reset</code> |
| |
| * If all of the above troubleshooting does not solve the problem, post to the POPFile Help Forum https://sourceforge.net/forum/forum.php?forum_id=213100 for further help. | * Microsoft [[http://support.microsoft.com/kb/811259 | lists]] a bunch of more heavy duty techniques you can try. In the end it seems comes down to uninstalling Window's TCP/IP Protocol and reinstalling it. It doesn't sound like you need your Windows disk but you might find it just in case if your computer came with one. |
| | |
| | * If nothing has worked and you are using Windows XP, open the command prompt and run ''sfc /scannow''. You will need your Windows CD (or Recovery CD) if your computer came with one. This utility scans for Windows files that have been modified from the original and replaces them. This will probably require you to run Windows Update again to download updates. Be sure your firewall is working and get those updates before you use the internet again since your computer is not protected with the latest updates. |
| | |
| | * The last method to try (other than reinstalling Windows) is a [[http://www.michaelstevenstech.com/XPrepairinstall.htm | Windows XP Repair Install]]. You must be very careful and follow the instructions exactly and read each screen carefully to prevent from loosing all your files. You will need a Windows XP CD (an Operating System Restore disk will not work). This option replaces all your Windows files back to the original install state, you will have to download a lot of Windows updates before your computer is safe to use on the internet again. Be sure you have a good backup of your files just in case before you try this, it is easy to make a mistake telling install to format your drive. Follow the instructions on the linked website carefully. If you are not comfortable doing this, **do not try it**, find someone who knows what they are doing. The POPFile developers will not be responsible for any data loss that may occur. |
| |
| | * **If all of the above troubleshooting does not solve the problem, post to the [[/discussion/1 | POPFile Help Forum]] for further help.** |
