Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Apr 10 09 4:04 am
Hi,
I am new to WinGate and I am trying to setup the software correctly. Here is my situation
I have installed WinGate on server 192.168.1.149
This Server is a domain controller with Active Directory.
This server is also the DNS and DHCP server in the Lan
The wingate installation went fine on ther server. I would like to be able to setup my client machines on the LAN using my Group Policy to push the Wingate address as a Proxy Server in order to view visited webpages of the clients.
I tried setting up a client manually.
In IE I did setup the Connextion => Proxy to point to 192.168.1.149 Port 1080 which is Socks Proxy in Wingate.
The Client has DHCP and the DNS Server is pushed as 192.168.1.149. The Gateway is pushed as 192.168.1.1 which is the Router's address.
When I try to connecte to the Internet, I get "Internet Explorer Cannot Display the wepage"
In Wingate on the server, I get "Authentication failed - user Guest on 192.168.1.12 requested SOCKS"
In Wingate I have correctly setup the DNS Resolver as 192.168.1.149
I have also Disabled DHCP and DNS in WinGate.
Anybody has any idea what is wrong in my setup?
Regards,
Mark
Apr 11 09 4:15 pm
mrhyman wrote:I tried setting up a client manually.
In IE I did setup the Connextion => Proxy to point to 192.168.1.149 Port 1080 which is Socks Proxy in Wingate.
The Client has DHCP and the DNS Server is pushed as 192.168.1.149. The Gateway is pushed as 192.168.1.1 which is the Router's address.
So you have a single NIC in the server and clients are connecting on the same subnet, or is there two NIC's in the Wingate Server and both on the same subnet?
Any particular reason why you want to use Socks?
Try this, on a client as a test set the proxy to point to the IP of your server and the WWW Proxy port of 80 [or other if not default].
mrhyman wrote:When I try to connecte to the Internet, I get "Internet Explorer Cannot Display the wepage"
In Wingate on the server, I get "Authentication failed - user Guest on 192.168.1.12 requested SOCKS"
I think the user should be allowed if Wingate is synchronising it's user database from AD? You can modify the User area in the System tab.
mrhyman wrote:In Wingate I have correctly setup the DNS Resolver as 192.168.1.149 I have also Disabled DHCP and DNS in WinGate.
Anybody has any idea what is wrong in my setup? Regards, Mark
Probably here you should point the resolver at the router, however Wingate will usually 'discover' DNS servers for you and this isn't always necessary to make any changes in this area.
Drop back and let the forum know how you get on.
Apr 13 09 11:06 am
Hi Nev,
Thanks a lot for replying to my post. I have tried all you suggestions.
First of all I have 2 NIC on the server but I am using only 1 right now. I thought this was the easiest path since I am new to Proxys and WinGate.
I have no particular reason for using SOCKS, the only think I would like to be able to do is to configure the IE proxy setting through my Group Policy on my server and that way I can push it to the client machines on my LAN that I want to monitor with WinGate.
When I setup the Client Machine (I go into IE and Connection Settings and in LAN settings I set the proxy address to 192.168.1.149 and port 80, which should be the WWW Proxy service and port of WinGate on the server. When I open IE in the client I get Page under Construction which is the page of IIS running on that same server. However I get no activity in WinGate.
I also Tried pointing the DNS Resolver to the Router's IP but that did not help either.
Any advice or tips will be most welcome since I really need to monitor my clients machines in the LAN.
Apr 14 09 4:30 pm
Ok I see!
What you could do is in the WWW proxy service on the Wingate machine, move the port to say 8080 and save that, it cannot work with two services on the same port on a single server.
Try a client to point to that instead as there is a conflict by the look of it with your IIS on the same port in the server.
With the two NIC's in the server, one should be internal with just an IP and mask, no gateway, the other NIC should be external and have the arrangements required for your Internet // router, IP, mask and it's gateway.
Check the usage in the network tab of Gatekeeper, that they are internal // external as required.
Apr 15 09 3:04 am
Thanks for your advice,
I have changed the port of the WWW Proxy Server to 8080 and it seems I got a bit further.
Now when I try to browse I get Authentication failed for user Guest but I can see the requested URL on the client machine.
If However I go to the PRoperties Section of the WWW Proxy Server and I set Authentication where required by Policies to Basic, on the client machine I get a prompt for username and password. When I enter my domain credentials I can browse and I can see the activity in gatekeeper. However this is a bit painful since each time I open Explorer I have to enter those credentials. Is there a way to authenticate the user without getting this prompt?
I think I am almost there. Thanks a lot for your support.
Mark
Apr 15 09 12:55 pm
Ok Mark that is progress.
With the authentication you can vary the needs in the System tab // Database options, you'd probably want to use the AD entry here to allow users' in Wingate.
You should also set the properties then in each service [WWW proxy] if required to allow // authenticate to suit your network.
Apr 16 09 3:03 am
Hi Nev,
I am using the AD Database and I cannot seem to get the users authenticated without User Name Password.
In the WWW Proxy Service I did setup the Policy to Everyone - User Maybe be unknown. I have also tried to User May be assumed and User must be authenticated.
Nothing works.
Either I get the password prompt on the client or I get
Socket Error - Socket Error 10049 {Thd 5968} [socket #DE0, 0.0.0.0:1252 to :0]
Apr 16 09 5:31 am
I have made some changes. After a lot of reading I configured my Client Machine to use the Gateway 192.168.1.149 which is the Domain Controller where Wingate is installed. Instead of using The Router's IP as gateway.
I now don't have to use proxy and I can see Activity and I can also see the History of Navigations.
However, what I see is IP addresses as NAT. I do not see that user X requested URL www. something.
Is there a way to do this now?
Mark
Apr 16 09 2:19 pm
Right Mark, what you could do is:
push to the clients [or configure] a proxy setting for the Wingate server IP and Port for all browser Internet Options
or, in the WWW Proxy you can enable Intercepts in the Sessions field this will put NAT web requests through the proxy
Option one is the preferred way.
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.