> Home > Knowledge Base > FreeProxy Knowledge Base > I2043: Email still not working, what do I do ?
 
Hi Guest
IP: 18.207.157.152

Username
Password
I2043: Email still not working, what do I do ?
Summary
Product: FreeProxy
Versions: 3.5 or later
Note: 2043
Date reported: 08 May 2004

Issue Detail
After following the instructions I still cannot connect to email.

Solution
Please follow this checklist.

1. After making the changes to configure FreeProxy, did you stop and start FreeProxy ?

2. FreeProxy must be running on the computer connected to the internet and that there are working network connections between the client and the server. You should be able to ping (see below) the client from the computer running FreeProxy and visa versa.

3. Do you have a firewall ? If you do, it is very likely (almost certain) that it is blocking the email ports. Make sure that the ports 110 and 25 (and any other ports you may be using for email) are open (not blocked)

4. In your email client check that the server name you use is either the name or IP address of YOUR server running FreeProxy NOT the name or IP address of the email server. Remember your email client connects to FreeProxy.

5. In FreeProxy check that the client port numbers are correct and match the port numbers you are using in the email client. You would normally be using ports 25 and 110. If you are using different port numbers check again that the client port in FreeProxy matches the port number you have specified in the email client.

6. If you have set local binding, check that the IP address you have set for both the incoming and outgoing mail in FreeProxy is the IP address of the local LAN. The IP address must not be the internet address.

7. Check that the mail server names you have specified in FreeProxy are the names or IP addresses of the email server at your ISP. Check that the port numbers are correct (usually 25 and 110).

To ping do the following:

In windows 98:
Select Start -> Run, and then fill in the word command and press OK
When the windows console appears, type in the following:

ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

In NT/2000/XP/2003:

Select Start -> Run, and then fill in the word cmd and press OK
When the windows console appears, type in the following:
ping 192.168.0.1
the results are similar to those for WIN98

If you get an error message it means that the network connections are not set up correctly.

Rectified
n/a
Hand-Crafted Software.
MemHT Portal is a free software released under the GNU/GPL License by Miltenovik Manojlo