Dec 17 10 2:20 am
Dec 17 10 2:29 pm
Dec 21 10 3:58 am
Dec 21 10 5:13 am
Dec 21 10 5:20 pm
I see that the trial version is enterprise 250 user... is it correct?
1) I setup the WWW proxy to enable access to everyone, and then the client to access trought the port 80.
But, on client, I get the message: You don't have right to access to this service.
So I setup the Assumed Users on the local IP of client: now it works correctly.
I would like this configuration:
client -> proxy (wingate) -> router -> server pop3 or imap
I don't want to store email on local server or on wingate.
using the http://www.mydomain.com -> error "impossible to find host"
using the IP of mydomain -> OK we receive email correctly
Dec 22 10 12:42 am
MattP wrote:This sounds like you have a DNS/NAT error, are your LAN clients able to resolve any domain names from the command line? If WinGate is in a gateway scenario, then we would suggest that you set your LAN clients' default gateway and DNS server settings to point at the WinGate server, this way, DNS resolution requests will work. The exception is if you're running an AD and your AD DNS server is a different machine to the WinGate server, in which case you will point your clients at that machine and then set a forward zone in your AD DNS server. You'll also want to add the IP address of the AD DNS server to the list of DNS servers in Start::Programs::WinGate::Advanced Options to avoid a DNS loop.
MattP wrote:It sounds like you don't want to use the WinGate mail services, so you should stop them.
MattP wrote:That sounds like you've created an access restriction policy that is denying access. Can you start off with no policies and verify that connection is ok? If you have created a policy that requires authentication then you must also select some form of authentication from the General tab.
MattP wrote:For your services, when you say that you set up the proxy (FTP and Telnet) to enable access for two users, did you create a location based policy, or a user based policy? Can you try authenticating with Internet Explorer and then connecting via Telnet on port 23?
Dec 22 10 5:04 am
criRV wrote:So I change the client DNS in the network properties FROM Server IP TO Isp DNS IP and all work
Dec 22 10 8:32 pm
Dec 23 10 1:18 am
Dec 23 10 2:01 am
Dec 23 10 4:52 pm
how can I access to your ticket system? (my forum email and password don't work).
Now I can do any operation without proxy settings on my client..... This is nice but I don't want it... it's seams I'm directly connected to internet.....
Is there something to do to secure Wingate? Or my actual config it's ok?
If I buy ie. wingate professional can I, after, upgrade to enterprise?
I see you are working on Wingate 7... what about if I want to upgrade from ie: Wingate 6 standard to Wingate 7?
Can we buy from your site or have we to buy from a national reseller?
Jan 02 11 5:13 am
Jan 11 11 8:53 am
MattP wrote:Can you please remove the DNS settings from the LAN adapter on your WinGate server? If you are using Active Directory then the DNS settings on your clients will need to point at the AD DNS server. You should also re-enable the DNS service in WinGate.
MattP wrote:CriRV wrote:Now I can do any operation without proxy settings on my client..... This is nice but I don't want it... it's seams I'm directly connected to internet.....
..... The clients are not connected directly to the Internet as they have to connect through WinGate to reach the Internet, which means that you can block access to all ports if you want to, and only allow connections on specific ports.
MattP wrote:If you want to be able to access your external email directly, without using WinGate, then you'll have to allow your clients to resolve DNS requests. I suppose that you could use IP addresses in the Email settings, but it would be easier to just allow DNS requests by setting the DNS on the clients to point at the WinGate server.