Socket Error

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Socket Error

Postby controlair » Sep 11 04 6:47 am

Hi all,
My clients are getting Socket Errors. I have even checked that I can browse fine from the proxy's desktop while proxy clients get the Socket Error.

I am running WinGate 5.0.2 on a Windows2000 Server in an Active Directory Windows 2000 network.

Clients are DHCP and use port 80 for the proxy.

Web browsing works find for certain periods of time then for about five minutes (approx.) all clients get Socket Errors. Then after this period browsing continues as normal. This is an ongoing cycle. Can you help? Below are the results of a 'route print'

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 04 75 8b 2b 48 ...... 3Com EtherLink PCI
0x1000004 ...00 04 75 8f c4 b5 ...... 3Com EtherLink PCI
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 64.169.216.38 64.169.216.33 1
0.0.0.0 0.0.0.0 172.22.10.1 172.22.10.17 2
0.0.0.0 0.0.0.0 172.22.10.3 172.22.10.17 3
64.169.216.32 255.255.255.248 64.169.216.33 64.169.216.33 1
64.169.216.33 255.255.255.255 127.0.0.1 127.0.0.1 1
64.255.255.255 255.255.255.255 64.169.216.33 64.169.216.33 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.22.0.0 255.255.0.0 172.22.10.1 172.22.10.17 1
172.22.10.0 255.255.254.0 172.22.10.17 172.22.10.17 2
172.22.10.17 255.255.255.255 127.0.0.1 127.0.0.1 2
172.22.14.10 255.255.255.255 172.22.10.3 172.22.10.17 1
172.22.20.10 255.255.255.255 172.22.10.3 172.22.10.17 1
172.22.40.0 255.255.255.0 172.22.10.4 172.22.10.17 1
172.22.60.0 255.255.255.0 172.22.10.4 172.22.10.17 1
172.22.70.10 255.255.255.255 172.22.10.3 172.22.10.17 1
172.22.255.255 255.255.255.255 172.22.10.17 172.22.10.17 2
224.0.0.0 224.0.0.0 64.169.216.33 64.169.216.33 1
224.0.0.0 224.0.0.0 172.22.10.17 172.22.10.17 2
255.255.255.255 255.255.255.255 172.22.10.17 172.22.10.17 1
Default Gateway: 64.169.216.38
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
172.22.0.0 255.255.0.0 172.22.10.1 1
172.22.40.0 255.255.255.0 172.22.10.4 1
172.22.60.0 255.255.255.0 172.22.10.4 1
CACC
controlair
 
Posts: 7
Joined: Sep 11 04 6:42 am

Postby controlair » Sep 11 04 12:16 pm

Here is the full error message:

Socket Error

Connection to Remote Host timed out
CACC
controlair
 
Posts: 7
Joined: Sep 11 04 6:42 am

Postby adrien » Sep 11 04 12:37 pm

Hi

I note you have 3 default routes. To your computer this means you have 3 paths to the Internet. If any of these gateways aren't actually a path to the Internet, then troubles follow.

The 2 default routes pointing to the private addresses - are they pointing to an internal router going to other subnets? If so, you are best to replace the default gateway settings with specific routes to those specific subnets, then the poor router on your machine won't have to try and choose between 3 roads to travel to the same destination, some of which may be dead-ends.

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Postby controlair » Sep 15 04 10:45 am

I removed the second route:
0.0.0.0 0.0.0.0 172.22.10.1 172.22.10.17 2

which was looking for a DSL connection that didn't exist. This seems to have solved the problem. Thanks!
CACC
controlair
 
Posts: 7
Joined: Sep 11 04 6:42 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 8 guests