Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

wingate 6.01 with MS server 2003 SBS 2003

Sep 02 04 12:59 am

greetings, encountering problems with wingate 6.01 995 on server with small business server 2003 running exchange server and server 2003 etc on board a ship.

I have disabled DHCP, DNS, SMTP and POP3 services in Wingate, using these services from the MS server 2003. Wingate server runs, clients do not automatically see server on install but when name IP address entered this works OK.

Clients can see server's companyweb / sharepoint web, exchange server and everythin internal, but cannot get access to any external internet sites. Wingate has 2 dial up interfaces configured, these are not triggered to dial - even if the connection is made manually from wingate server, clients still have no access.

The WWW / http service in wingate gets an error starting up and has a red circle with exclamation mark. Wingate server uses the NT database and imports users OK, I configure users access to 2 interfaces but no request for dial or interface choice is given on the client.

Any help would be greatly appreciated.

Jon

Sep 02 04 1:48 am

Hi

If there is an exclamation mark in the WWW Proxy, that usually indicates a port conflict.

Most likely IIS is running on that server on port 80, and stopping the WWW Proxy from starting properly. If you aren't using IIS, you should be able to simply stop the "web publishing service" from starting in control panel: administrative settings: services.

Adrien

Stopping IIS

Sep 02 04 2:05 am

Adrien, thanks for your swift reply. Currently users run basic services (share documents, add notices etc.) from the MS server's company web site on the server. If IIS is stopped will this stop or limit users access to the companyweb ?

Sorry, I am not very knowledgable on sharepoint/IIS etc.

If this does limit the internal company web operation is there another workaround (change port settings) ?

Sep 02 04 10:35 am

It will most likely affect your company web-site if you stop IIS. Your easiest option would probably be to change the proxy port on WinGate.

Are you using the WinGate Internet Client, proxy OR NAT to connect ?
Post a reply