WinGate Internet Client and Apache 2.2 Server...

[skaughtEE]

Hello all,

I have been attempting to get the Joomla CMS up and running on my laptop which requires an Apache server. I downloaded the most recent version and installed it but it would never start. I was constantly getting errors. I checked out various articles on the internet and found that it had something to do with the Winsock.dll and that things were being intercepted before they were getting to the Apache server.

I have been running the Wingate Internet Client in order to connect to the Wingate server (as I was having other issue using NAT) and so I decided to uninstall this to see if it was the culprit.

Suddenly, not to my complete surprise, my Apache server was up and running.

But then I was not able to access the internet as I need the Wingate Internet Client.

Anyway, here is the error from the Apache server that appears in the error log file:

[Thu Sep 20 12:34:37 2007] [crit] (OS 10091)WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. : Child 1912: setup_inherited_listeners(), WSASocket failed to open the inherited socket.

I am not sure if anyone else has run into this issue or not, but if you have and you have found a way to resolve the issue then I would greatly appreciated any suggestions that you might have to offer.

Thanks, and take care.

..scoTT

[genie]

LSP support in Windows is notorious for breaking various applications. Looks like Apache is one of them. Why can't you use NAT?

[skaughtEE]

I am not quite sure what happened with my ability to use NAT. All that I know is that about a year ago it stopped working for me when I ran an update. I can't recall if it was 6.1 or 6.2.

I am able to pick up my email through Outlook, but whenever I attempt to browse the internet it just sits there and nothing comes back. I can watch the NAT with the IP address in the Gateway, but it never returns any pages. That is when I installed the Wingate Internet Client and then everything worked.

I would, given my current issue with the Apache server, prefer to run my connection straight through the Wingate server using NAT as opposed to the WGIC.

Again, if there are any suggestions as to how to get these two things working together, they would be greatly appreciated.

Thanks, and take care.

..scoTT

[genie]

My suggestion would be to fix NAT:
1. Make sure your default gateway leads through Wingate machine
2. Make sure there is a route from Wingate machine back to the client
3. Make sure Wingate machine interfaces are properly marked internal/external

[skaughtEE]

Hi,

I have points 1. and 3. covered as I read last night the one post about common errors and it mentioned about setting the adapters properly.

How do I make sure that I have a route back to the client? I am not quite sure about this point.

Thanks, and take care.

..scoTT

[genie]

Well, try pinging the server from the client - if it works, try pinging some external site from the client. Then try connecting to a WWW site from the client - make sure WWW session interception is off (just for the sake of testing NAT properly).