Moderator: Qbik Staff
omg900 wrote:Hi folks!
I am using wingate 5.0.2 on a Win2K ADV Server as a gateway to the internet for 4 workstations. Server and workstations have static private IP's. All works fine and no probs at all. However when I update to Wingate 5.2.2 nothing works (neither the server nor the workstations have internet access). The wingate log shows the following:
12/18/03 12:11:07 192.168.58.14 og4 0000000012 Requested: http://www.microsoft.com/
12/18/03 12:11:29 192.168.58.14 og4 0000000012 Error: Caught socket exception in CWWWSession::HTTPProcessRequest() Connection to Remote Host timed out - terminating
12/18/03 12:11:30 192.168.58.14 og4 0000000012 Traffic 215 419 0 0 23s
Any clue why this might happen and why there is thi problem with wingate 5.2.2 and not with version 5.0.2 ????
Appreciate any enlightment.
omg900 wrote:Hi folks!
I am using wingate 5.0.2 on a Win2K ADV Server as a gateway to the internet for 4 workstations. Server and workstations have static private IP's. All works fine and no probs at all. However when I update to Wingate 5.2.2 nothing works (neither the server nor the workstations have internet access). The wingate log shows the following:
omg900 wrote:Hi Pascal,
what do you mean by T/R? I am having fixed IP-Numbers and I believe I am using the proxies directly. For example www-proxy is set for port 8081. Server is 192.168.58.112 and workstations are 192.168.58.113-117. Internet Explorer on the workstations points to the server IP on Port 8081.
Nevertheless how comes my set-up works fine with wingate 5.0.2 and does not with wingate 5.2.2? Has something changed?
Best regards and wishing you merry x-mas and a happy new year!
omg900 wrote:Pascal, have you had a chance to look into this? I believe Nicholasf has the same problem ...
omg900 wrote:Pascal, have you had a chance to look into this? I believe Nicholasf has the same problem ... Brgds
Pascal wrote:omg900 wrote:Pascal, have you had a chance to look into this? I believe Nicholasf has the same problem ... Brgds
A quick thought ... can you (For a test) set the WinGate service to be "Manual Start" in the Service Control Manager. Reboot the PC and start the WinGate Server manually. Then check if your internal IP is visible. Let me know then, please. If it is not, then you can switch it back to automatic start.
genie wrote:Hi, Oliver
Can you turn on debug mode for ENS and see what kind of log messages it generates?
omg900 wrote:OK, I will keep quiet and check for posts from time to time. If ou require any other logs just let me know.
Brgds
Oliver
omg900 wrote:omg900 wrote:OK, I will keep quiet and check for posts from time to time. If ou require any other logs just let me know.
Brgds
Oliver
Still no luck in tracing the bug? It seems I am not the only one with this problem ... Appreciate your feedback.
Brgds
Oliver
Jason Dax wrote:Just a sugestion, in case you don't have tried:
1) Don't Upgrade. Take a note of your actual config, uninstall, reboot and make a clean install. See if the default config gave the same problem.
2) Have you tried to change the NICS? I have found that some hardware is not compatible, or at least misconfigured when installed. (TX/RX settings, something like that).
And don't expect a fast response from qbik: seem to be that they have a lot of work to see this "little problems". :)
Regards.
genie wrote:Hi, Oliver
Sorry for keeping you waiting - I was on vacation for a while.
Can you update the NIC driver to the latest one? If it does not solve the problem, drop me an email - I'll send you the new driver for testing.
Gene
Users browsing this forum: No registered users and 5 guests