Question

Locked

Squid Configuration

By bomjan23 ·
Dear all,
I am trying to configure a squid proxy server for my office where the clients are supposed to access internet through our locan domain.
My internet connection is via a P2P leaseline of 128KbpS
and when i run teh following command there is an error message as shown below.

Kindly Comment

Thanks in advance.


# /sbin/service squid start
Starting squid: /etc/init.d/squid: line 53: 6156 Aborted $SQUID $SQUID_OPTS >> /var/log/squid/squid.out 2>&1
[FAILED]
#

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Go here for your answer..

http://learnlinux.tsf.org.za/courses/build/electives/ch03s03.html

Please post back if you have any more problems or questions.

Collapse -

Thank you for the support

by bomjan23 In reply to Squid Configuration

In fact the suggestion advised was really helpful however the problem still persists as of now.

The main scenario is as mentioned earlier we use a P2P lease line and have configured our router from the service provider.

Now the international link (DNS) has failed in the service provider for which they changed the DNS and we also changed it in our router and the Proxy server.
How ever I an access internet on my Proxy server but the clients on the other hand cannot still access as they are connected through our own DNS server. We do not use DHCP hence all IP are static.

But the main concern is I can ping google or yahoo from the client and even can access messenger and can even receive and send mails using outlook but can still not view any websites.
So, What could be the possible suggestions.

Collapse -

Try these out to see if they repair your connections....

Repairing Damaged Winsock2
The symptoms when Winsock2 is damaged shows when you try to release and renew the IP address using IPCONFIG.
And you get the following error message:
An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket.
Also Internet Explorer may give the following error message:
The page cannot be displayed Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.
-----
If you have WindowsXP with Service Pack 2, there is a one line command you can run to reset the winsock2 registry entries
netsh winsock reset catalog
------
There are two easy ways to determine if Winsock2 is damaged:
From the XP source files, go to the Support / Tools directory
Winsock Test Method 1
Run netdiag /test:winsock
The end should say Winsock test ..... passed
Winsock Test Method 2
1.Run Msinfo32
2.Click on the + by Components
3.Click on the by Network
4.Click on Protocol
5.There should be 10 sections if the Winsock2 key is ok
MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
MSAFD NetBIOS [\Device\NetBT_Tcpip...
If the names are anything different from those in this list, then likely Winsock2 is corrupted and needs to be repaired.
If you have any 3rd party software installed, the name MSAFD may be changed.
There should be no fewer than 10 sections.

To repair Winsock2
1.Run Regedit
2.Delete the following two registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

3.Restart the computer
4.Go to Network Connections
5.Right click and select Properties
6.Click on the Install button
7.Select Protocol
8.Click on the Add button
9.Click on the Have Disk button
10.Browse to the \Windows\inf directory
11.Click on the Open button
12.Click on the OK button
13.Highlight Internet Protocol (TCP/IP)
14.Click on the OK button
15.Reboot
Or Download Reg file:
http://www.onecomputerguy.com/reg/xp_winsock.reg
to add the correct registries back in. Then reboot the computer.

OR try this out..........

Fix your DNS problems
If you're having problems Web surfing, you may have a DNS problem. Here are quick ways to fix it.
DNS, though, can be your foe as well as your friend. DNS problems may stop you from being able to visit Web sites. If you're having problems connecting, it doesn't take much work to see if DNS is the cause, and if it is, to try to fix it.
To find out whether DNS is a potential culprit when you're having trouble connecting to a site, first ping the site to which you can't connect by issuing the ping command at the command prompt, like this:
ping www.computerworld.com
If the site is live, you'll get an answer like this
Pinging www.computerworld.com
[65.221.110.9 with 32 bytes of data:

Reply from 65.221.110.98: bytes=32
time=22ms TTL=235
Reply from 65.221.110.98: bytes=32
time=23ms TTL=235
Reply from 65.221.110.98: bytes=32
time=23ms TTL=235
Reply from 65.221.110.98: bytes=32
time=24ms TTL=235

Ping statistics for 65.221.110.98:
Packets: Sent = 4, Received = 4,
Lost = 0 (0% loss),
Approximate round trip times in
milli-seconds:
Minimum = 22ms, Maximum = 24ms,
Average = 23ms
If it's not, you'll get a response like this:
Ping request could not find host.
Please check the name and try again.
If you ping a site and it's live but you can't connect to it with your browser, a DNS problem might be the reason. If you suspect you're having a DNS problem, take the following actions:
Check your HOSTS file
If your HOSTS file contains an incorrect or outdated listing, you won't be able to connect. Even if you don't recall adding listings to a HOSTS file, it still might contain listings, because some Internet accelerator utilities edit them without telling you. Open your HOSTS file with Notepad and see if the site you can't connect to is listed there. If it is, delete the entry, and you should be able to connect.
For details about editing a HOSTS file, see "Hack DNS for lightning-fast Web browsing."
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9019951
Check your DNS settings
Make sure your DNS settings are correct for your ISP or network. If you've changed your DNS settings to use a service such as OpenDNS, for example, you might have entered them incorrectly.
Find out from your ISP or network administrator what your DNS settings are supposed to be, or check the OpenDNS site (or another DNS service) for their server settings. Once you've done that, you'll need to make sure that you've entered the DNS settings properly.
Check the article "Hack DNS for lightning-fast Web browsing" for details about how to change your DNS settings. Then change the DNS servers to the proper ones, or choose "Obtain DNS server address automatically" if your ISP or network administrator tells you to use that setting.
Flush your DNS cache
The problem might be related to your DNS cache, so flush it out. To flush the cache, type ipconfig /flushdns at a command prompt.
Find out if your ISP is having DNS problems
Your ISP could be the source of the problem. One possibility is that one of its DNS servers is down and you're trying to access the downed server. If you know the addresses of the DNS servers, ping each of your ISP's DNS servers, and if any of them don't respond, remove them from your DNS list.
If you don't know the address of the DNS servers and you're supposed to use the choose "Obtain DNS server address automatically" setting, you'll have to call your ISP to see whether its DNS servers are having problems. Alternately, you can use the OpenDNS servers instead of your ISP's DNS servers. For details, see "Hack DNS for lightning-fast Web browsing."
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9019951

Please post back if you have any more problems or questions.

Back to Networks Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums