When use NAT, wingate DNS server is not stable.

[gjethro]

The problem is

The lan have a domain controller 192.168.1.10,
wingate server ip address is 192.168.0.1, 192.168.1.1 and using ADSL,
Setting for lan's pc behind the wingate server is:
the DNS setting
--192.168.1.1
--192.168.1.10
the IE setting (Use NAT)
---clear all setting in the LAN settings of connections of internet options

From the lan's pc behind the wingate server

IE can display the page of www.qbik.com(almost always), ping www.qbik.com can get ip address.
BUT sometime IE says "The page cannot be displayed" and display some errors WHEN surf to your forums(forums.qbik.com), when I ping forums.qbik.com get unknow host, sometime it do ok.
(NOTE:The wingate server always ok!)

sometime, I disable the local connection in lan's pc and enable it again, it will work, but sometime it will not.

This also happen to other sites, even the biggest gate site,
For example, now, I can use your forums(forums.qbik.com) to post this request, but I can not surf to www.sina.com.cn, www.sohu.com and so on.

(NOTE: if use proxy server, IE always work)

it's very stange!!!

[gjethro]

Ha ha,After i post the pre request, I restart my pc. It's more stange: All the sites cannot be get , include yours and MSN Messager cannot connect to server. I have to use the proxy server to post this request!!!

But this morning, After restart, it all work.

[adrien]

We found an issue with 5.2 which we fixed in 5.2.2 where scanning could get blocked if a client disconnected from an HTTP session whilst the file they were retrieving was being scanned, this eventually would block all web access.

Did you see this behaviour with version 5.2, or 5.2.2?

Adrien

[gjethro]

Adrien,

I use wingate V5.2.2, the lastest version.
pls be carefully, I didn't say "block all web access", just the DNS run into Problem! or how can I post the 2nd request to you?

pls read the pre request!

Thanks.

[adrien]

OK, but the error that IE displays when it can't connect to a site for some reason is "DNS or server error", when quite often it has nothing to do with DNS. This can be quite misleading.

There are a few things you can check.

If not, what DNS servers are specified to be used in the TCP/IP properties of your network adapters (in the OS) - WinGate will try to use these DNS servers.

You can also manually add DNS servers to WinGate's DNS resolver in GateKeeper, and then these will be used in preference to any discovered from the OS.

What this means is that (taking another look at your post) there is a problem if you have specified the IP address of the WinGate machine as being one of the DNS servers for the WinGate machine to use, since when it starts asking itself, it will create DNS lookup loops.

There are many things that can cause WinGate to start using a different DNS server, if it knows several, for instance if one DNS server doesn't respond to a request, WinGate will try several the next retry. This could cause an intermittent loop if for instance the second DNS server specified was the IP of the WinGate machine itself.

Adrien

Adrien

[gjethro]

Hi,

First , to the most extent, I can confirm it is DNS problem, because:
1. If dns is Ok, ping forums.qbik.com should get IP Address at least, should not get unknow host(pls read my 1st request), as it do when it work.
2. nslookup confirmed It's reported by wingate that cannot find the IP Address.

Second, My ADSL get DNS server automatic, I think it work. because the problem will not occur in wingate server and will not occur when i don't use NAT(e.g. use www proxy server for IE) in pc behind wingate server, Even when I use NAT, sometime it will not occur and sometime it will only occur to some site(e.g. in the same time, www.qbik.com is ok but forums.qbik.com don't work, pls read my 1st request),so I said it's not stable.

Finnally,After I have manually added DNS servers to WinGate's DNS resolver in GateKeeper, It seems the same as get DNS server automatic,
but I didn't check it carefully.

Thanks

[gjethro]

Hi...
Now I give the Configuration Report of gatekeeper to u:

1.01 WINGATE CONFIGURATION REPORT
1.02 Monday, December 15, 2003, 10:31
1.03
1.04 ---------------------------------------------
1.05 WinGate Engine
1.06 ---------------------------------------------
1.07 WinGate 5.2.2 (Build 892)
1.08 Operating System: Windows 2000 (NT 5.0)
1.09 Language:
1.10
4.01 ---------------------------------------------
4.02 Dialer information
4.03 ---------------------------------------------
4.04 Dialer is enabled
4.05 Profiles:
4.06 ADSL Dial (Enabled) 1000 retries
4.07 Overall retries: 1
4.08
5.01 ---------------------------------------------
5.02 Network Interfaces
5.03 ---------------------------------------------
5.04 169.254.147.67 (LAN) [External] [Unsecure]
5.05 127.0.0.1 (LOOPBACK) [Internal] [Secure]
5.06 192.168.1.1 (LAN) [Internal] [Secure]
5.07 ADSL Dial (RAS) [External] [Unsecure]
5.08
6.01 ---------------------------------------------
6.02 Services
6.03 ---------------------------------------------
6.04
6.05 System Policies
6.06 ---------------------------------------------
6.07 Default System Access Rights:
6.08 Full Access - Restricted by security level
6.09 Default Start/Stop Rights:
6.10 Administrators - Unrestricted rights
6.11 Default Edit Rights:
6.12 Administrators - Unrestricted rights
6.13
6.14 POP3 Proxy server (POP3 Proxy server)
6.15 ---------------------------------------------
6.16 Session Timeout: 120
6.17 Port: 8110
6.18 Startup: Automatic start/stop
6.19 Binding 1: 127.0.0.1
6.20 Binding 2: 192.168.1.1
6.21 Access Rights: Defaults: may be used instead
6.22 Start/Stop Rights: Defaults: may be used instead
6.23 Edit Rights: Defaults: may be used instead
6.24
6.25 Telnet Proxy server (Telnet Proxy server)
6.26 ---------------------------------------------
6.27 Session Timeout: 60
6.28 Port: 23
6.29 Startup: Automatic start/stop
6.30 Binding 1: 127.0.0.1
6.31 Binding 2: 192.168.1.1
6.32 Access Rights: Defaults: may be used instead
6.33 Start/Stop Rights: Defaults: may be used instead
6.34 Edit Rights: Defaults: may be used instead
6.35
6.36 WWW Proxy server (WWW Proxy server)
6.37 ---------------------------------------------
6.38 Session Timeout: 60
6.39 Port: 80
6.40 Startup: Automatic start/stop
6.41 Binding 1: 127.0.0.1
6.42 Binding 2: 192.168.1.1
6.43 Access Rights: Defaults: may be used instead
6.44 Half Access - Restricted by security level, ban list, request
6.45 Working Access - Restricted by security level, request
6.46 Start/Stop Rights: Defaults: may be used instead
6.47 Edit Rights: Defaults: may be used instead
6.48
6.49 DHCP Service (DHCP Service)
6.50 ---------------------------------------------
6.51 Session Timeout: 60
6.52 Port: 67
6.53 Startup: Automatic start/stop
6.54 Binding 1: 192.168.1.1
6.55 Access Rights: Defaults: may be used instead
6.56 Everyone - Unrestricted rights
6.57 Start/Stop Rights: Defaults: may be used instead
6.58 Edit Rights: Defaults: may be used instead
6.59
6.60 Winsock Redirector Service (Winsock Redirector Service)
6.61 ---------------------------------------------
6.62 Session Timeout: 20
6.63 Port: 2080
6.64 Startup: Automatic start/stop
6.65 Binding 1: 127.0.0.1
6.66 Binding 2: 192.168.1.1
6.67 Access Rights: Defaults: may be used instead
6.68 Start/Stop Rights: Defaults: may be used instead
6.69 Edit Rights: Defaults: may be used instead
6.70
6.71 FTP Proxy server (FTP Proxy server)
6.72 ---------------------------------------------
6.73 Session Timeout: 60
6.74 Port: 21
6.75 Startup: Automatic start/stop
6.76 Binding 1: 127.0.0.1
6.77 Binding 2: 192.168.1.1
6.78 Access Rights: Defaults: may be used instead
6.79 Start/Stop Rights: Defaults: may be used instead
6.80 Edit Rights: Defaults: may be used instead
6.81
6.82 RTSP Streaming Media Proxy (RTSP Streaming Media Proxy)
6.83 ---------------------------------------------
6.84 Session Timeout: 60
6.85 Port: 554
6.86 Startup: Automatic start/stop
6.87 Binding 1: 127.0.0.1
6.88 Binding 2: 192.168.1.1
6.89 Access Rights: Defaults: may be used instead
6.90 Start/Stop Rights: Defaults: may be used instead
6.91 Edit Rights: Defaults: may be used instead
6.92
6.93 SOCKS Proxy server (SOCKS Proxy server)
6.94 ---------------------------------------------
6.95 Session Timeout: 60
6.96 Port: 1080
6.97 Startup: Automatic start/stop
6.98 Binding 1: 127.0.0.1
6.99 Binding 2: 192.168.1.1
6.100 Access Rights: Defaults: may be used instead
6.101 Start/Stop Rights: Defaults: may be used instead
6.102 Edit Rights: Defaults: may be used instead
6.103
6.104 VDOLive Proxy server (VDOLive Proxy server)
6.105 ---------------------------------------------
6.106 Session Timeout: 60
6.107 Port: 7000
6.108 Startup: Automatic start/stop
6.109 Binding 1: 127.0.0.1
6.110 Binding 2: 192.168.1.1
6.111 Access Rights: Defaults: may be used instead
6.112 Start/Stop Rights: Defaults: may be used instead
6.113 Edit Rights: Defaults: may be used instead
6.114
6.115 POP3 Server (POP3 Server)
6.116 ---------------------------------------------
6.117 Session Timeout: 120
6.118 Port: 110
6.119 Startup: Automatic start/stop
6.120 Binding 1: 127.0.0.1
6.121 Binding 2: 192.168.1.1
6.122 Access Rights: Defaults: may be used instead
6.123 Start/Stop Rights: Defaults: may be used instead
6.124 Edit Rights: Defaults: may be used instead
6.125
6.126 SMTP Proxy server for Netcomputer (SMTP Proxy server for Netcomputer)
6.127 ---------------------------------------------
6.128 Session Timeout: 60
6.129 Port: 29
6.130 Startup: Automatic start/stop
6.131 Binding 1: 127.0.0.1
6.132 Binding 2: 192.168.1.1
6.133 Access Rights: Defaults: may be used instead
6.134 Start/Stop Rights: Defaults: may be used instead
6.135 Edit Rights: Defaults: may be used instead
6.136
6.137 SMTP Server (SMTP Server)
6.138 ---------------------------------------------
6.139 Session Timeout: 300
6.140 Port: 25
6.141 Startup: Automatic start/stop
6.142 Binding 1: 127.0.0.1
6.143 Binding 2: 192.168.1.1
6.144 Access Rights: Defaults: may be used instead
6.145 Start/Stop Rights: Defaults: may be used instead
6.146 Edit Rights: Defaults: may be used instead
6.147
6.148 GDP Service (GDP Service)
6.149 ---------------------------------------------
6.150 Session Timeout: 60
6.151 Port: 368
6.152 Startup: Automatic start/stop
6.153 Binding 1: 127.0.0.1
6.154 Binding 2: 192.168.1.1
6.155 Access Rights: Defaults: may be used instead
6.156 Start/Stop Rights: Defaults: may be used instead
6.157 Edit Rights: Defaults: may be used instead
6.158
6.159 SMTP Proxy server for sohu (SMTP Proxy server for sohu)
6.160 ---------------------------------------------
6.161 Session Timeout: 60
6.162 Port: 27
6.163 Startup: Automatic start/stop
6.164 Binding 1: 127.0.0.1
6.165 Binding 2: 192.168.1.1
6.166 Access Rights: Defaults: may be used instead
6.167 Start/Stop Rights: Defaults: may be used instead
6.168 Edit Rights: Defaults: may be used instead
6.169
6.170 SMTP Proxy server for sina (SMTP Proxy server for sina)
6.171 ---------------------------------------------
6.172 Session Timeout: 60
6.173 Port: 26
6.174 Startup: Automatic start/stop
6.175 Binding 1: 127.0.0.1
6.176 Binding 2: 192.168.1.1
6.177 Access Rights: Defaults: may be used instead
6.178 Start/Stop Rights: Defaults: may be used instead
6.179 Edit Rights: Defaults: may be used instead
6.180
6.181 XDMA Proxy service (XDMA Proxy service)
6.182 ---------------------------------------------
6.183 Session Timeout: 20
6.184 Port: 8000
6.185 Startup: Automatic start/stop
6.186 Binding 1: 127.0.0.1
6.187 Binding 2: 192.168.1.1
6.188 Access Rights: Defaults: may be used instead
6.189 Start/Stop Rights: Defaults: may be used instead
6.190 Edit Rights: Defaults: may be used instead
6.191
6.192 DNS Service (DNS Service)
6.193 ---------------------------------------------
6.194 Session Timeout: 60
6.195 Port: 53
6.196 Startup: Automatic start/stop
6.197 Binding 1: 192.168.1.1
6.198 Access Rights: Defaults: may be used instead
6.199 Start/Stop Rights: Defaults: may be used instead
6.200 Edit Rights: Defaults: may be used instead
6.201
6.202 WWW Server for viewing log files (Logfile Server)
6.203 ---------------------------------------------
6.204 Session Timeout: 60
6.205 Port: 8010
6.206 Startup: Automatic start/stop
6.207 Binding 1: 127.0.0.1
6.208 Binding 2: 192.168.1.1
6.209 Access Rights: Defaults: may be used instead
6.210 Start/Stop Rights: Defaults: may be used instead
6.211 Edit Rights: Defaults: may be used instead
6.212
6.213 SMTP Proxy server for 163 (SMTP Proxy server for 163)
6.214 ---------------------------------------------
6.215 Session Timeout: 60
6.216 Port: 28
6.217 Startup: Automatic start/stop
6.218 Binding 1: 127.0.0.1
6.219 Binding 2: 192.168.1.1
6.220 Access Rights: Defaults: may be used instead
6.221 Start/Stop Rights: Defaults: may be used instead
6.222 Edit Rights: Defaults: may be used instead
6.223
6.224 Remote Control Service (Remote Control Service)
6.225 ---------------------------------------------
6.226 Session Timeout: 60
6.227 Port: 808
6.228 Startup: Automatic start/stop
6.229 Binding 1: 127.0.0.1
6.230 Binding 2: 192.168.1.1
6.231 Access Rights: Defaults: are ignored
6.232 Everyone - Unrestricted rights
6.233 Start/Stop Rights: Defaults: may be used instead
6.234 Edit Rights: Defaults: may be used instead
6.235
7.01 ---------------------------------------------
7.02 System Route Table
7.03 ---------------------------------------------
7.04 Current Route Table:
7.05 ---------------------------------------------
7.06 Network Mask Gateway Interface Metric
7.07 0.0.0.0 0.0.0.0 218.17.90.41 218.17.90.41 1
7.08 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
7.09 169.254.0.0 255.255.0.0 169.254.147.67 169.254.147.67 1
7.10 169.254.147.67 255.255.255.255 127.0.0.1 127.0.0.1 1
7.11 169.254.255.255 255.255.255.255 169.254.147.67 169.254.147.67 1
7.12 192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 1
7.13 192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 1
7.14 192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 1
7.15 218.17.90.1 255.255.255.255 218.17.90.41 218.17.90.41 1
7.16 218.17.90.41 255.255.255.255 127.0.0.1 127.0.0.1 1
7.17 218.17.90.255 255.255.255.255 218.17.90.41 218.17.90.41 1
7.18 224.0.0.0 224.0.0.0 169.254.147.67 169.254.147.67 1
7.19 224.0.0.0 224.0.0.0 192.168.1.1 192.168.1.1 1
7.20 224.0.0.0 224.0.0.0 218.17.90.41 218.17.90.41 1
7.21 255.255.255.255 255.255.255.255 169.254.147.67 169.254.147.67 1
7.22
8.01 ---------------------------------------------
8.02 Enhanced Network Support
8.03 ---------------------------------------------
8.04 Enhanced Network Support: 5.10 Syz - Installed and active
8.05 Driver: Enabled
8.06 NAT: Enabled
8.07 Router: Disabled
8.08 Firewall level: Custom
8.09
8.10 Firewall
8.11 ---------------------------------------------
8.12 Disable network name broadcasts to the Internet: Enabled
8.13 Allow users to ping this machine locally: Enabled
8.14 Allow users to ping this machine from the Internet: Disabled
8.15 Discard spoofed packets: Enabled
8.100
8.101 Port Security
8.102 ---------------------------------------------
8.103
8.104 Security for: External TCP
8.105 Action: Allow Port: 113 - AUTH
8.106
8.107 Security for: External UDP
8.108 Action: Allow Port: 1024 - 65535 - External
8.109
8.110 Security for: Internal TCP
8.111 Action: Allow Port: 21 - Hole for FTP Proxy server
8.112
8.113 Security for: Internal UDP
8.114
8.115 Security for: NAT TCP
8.116 Action: Allow Port: 21 - Hole for FTP Proxy server
8.117
8.118 Security for: NAT UDP
8.500
9.01 ---------------------------------------------
9.02 END OF CONFIGURATION REPORT

[ChrisH]

Hello,

When I look at your config. report, I would say only your Full Access users can use the WG DNS service. Is that what you want? Which machines have DNS problems? Is it usually the ones that non Full Access members use? Change to Everyone & default rights are ignored and see what happens.

[gjethro]

hi,

Yes, maybe i make a mistake, I have change to Everyone & default rights are ignored. if still has problem, I will trouble u again.

But all the Problem is happened when I use gatekeeper to login as administrator.

Thanks

[gjethro]

Hi...

The problem is still happened: it's not stable!!!

sometimes work, sometimes not, EVEN using administrator

For instance:
sometimes IE can open forums.qbik.com, sometimes not, sometimes even www.qbik.com cannot be opened.

BUT Proxy Server always Work!!!

Thanks.

[adrien]

Hi

The proxy server uses the same DNS resolver as the DNS server in WinGate does, so if the proxy always works, that means that the DNS resolver in WinGate is working.

If you aren't using the proxy, then the client machine will need to be able to resolve DNS. This means there can be an issue in your client DNS configuration, or the configuration of the DNS service in WinGate.

By the way, it is best to make the policies for the DNS service in WinGate so that anyone can use it, since there is no mechanism to authenticate with DNS, and DNS requests are normally the first thing a client will try and do before making any connection (which could then result in an authentication).

Adrien

[gjethro]

Hi,

I do know it is a trouble to u, But I want to know why? it's strange to me!
and I have sent all the configure to u in the pre post, pls help!!!


NOW, it seems work when disable the local Area connection(network card) and then enable it in controll panel when the problem happen.

Thanks

[adrien]

OK, I will look into the DNS server. That will be the service affected by the LAN adapter being reset like that.

most odd!

If you turn on debug logging in the DNS server, would you be able to send me the DNS service log file when this happens?

send it to adrien at qbik dot com

Adrien

[gjethro]

oK

[gjethro]

Hi,

I enable the debug log for DNS Service and DNS/WINS Resover,
When the problem occur, I ping/nslookup some site, Nothing is logged,
when i reset the LAN adapter, It works again, and both is logged.

Moment...
This Time I don't reset the LAN adapter, It's work again!!!, I just login
the wingate server and open ie to some site.

???

Thanks! Following is the snippet, I will sent a whole one to u later.

12/18/03 17:17:42 Request: request [0263c666] A lookup "www.cjol.com.Omnicare.com."
12/18/03 17:17:42 Debug: bounce request [0263c666]<0> to try 1 (nothing useful in cache)
12/18/03 17:17:42 Debug: selected 202.96.128.143 for request [0263c666]<1> (best looking)
12/18/03 17:17:42 Debug: request [0263c666](ID 1113) sent to 202.96.128.143 (43 bytes)
12/18/03 17:17:44 Debug: received block [91] (server 202.96.128.143, port 53)
12/18/03 17:17:44 Debug: added to cache from [0263c666]
12/18/03 17:17:44 Debug: completed [0263c666](ID 1113) (1.25s)
12/18/03 17:17:44 Request: request [0263c666] A lookup "www.cjol.com."
12/18/03 17:17:44 Debug: completed [0263c666]<0> (cache hit) (0.00s)
12/18/03 17:17:59 Request: request [0263c666] PTR lookup "1.1.168.192.in-addr.arpa."
12/18/03 17:17:59 Debug: completed [0263c666]<0> (cache hit) (0.00s)
12/18/03 17:17:59 Request: request [0263c666] A lookup "pop.163.com.Omnicare.com."
12/18/03 17:17:59 Debug: bounce request [0263c666]<0> to try 1 (nothing useful in cache)
12/18/03 17:17:59 Debug: selected 202.96.128.143 for request [0263c666]<1> (best looking)
12/18/03 17:17:59 Debug: request [0263c666](ID 1114) sent to 202.96.128.143 (42 bytes)
12/18/03 17:18:00 Debug: request [0263c666] "pop.163.com.Omnicare.com." (no response on try 1)
12/18/03 17:18:00 Debug: multicast request [0263c666]<2> (3 good servers)
12/18/03 17:18:00 Debug: request [0263c666](ID 1115) sent to 202.96.128.143 (42 bytes)
12/18/03 17:18:00 Debug: request [0263c666](ID 1116) sent to 202.96.134.133 (42 bytes)
12/18/03 17:18:00 Debug: request [0263c666](ID 1117) sent to 192.168.1.1 (42 bytes)
12/18/03 17:18:00 Debug: completed "192.168.1.1" (Internal reverse lookup - cache hit [0 ms])
12/18/03 17:18:00 Request: request [014ff62e] A lookup "pop.163.com.Omnicare.com."
12/18/03 17:18:00 Debug: bounce request [014ff62e]<0> to try 1 (nothing useful in cache)
12/18/03 17:18:00 Debug: selected 202.96.128.68 for request [014ff62e]<1> (best looking)
12/18/03 17:18:00 Debug: request [014ff62e](ID 1118) sent to 202.96.128.68 (42 bytes)
12/18/03 17:18:01 Debug: received block [90] (server 202.96.128.143, port 53)
12/18/03 17:18:01 Debug: added to cache from [0263c666]
12/18/03 17:18:01 Debug: completed [0263c666](ID 1115) (0.42s)
12/18/03 17:18:01 Request: request [0263c666] A lookup "pop.163.com."
12/18/03 17:18:01 Debug: bounce request [0263c666]<0> to try 1 (nothing useful in cache)
12/18/03 17:18:01 Debug: selected 202.96.128.68 for request [0263c666]<1> (best looking)
12/18/03 17:18:01 Debug: request [0263c666](ID 1119) sent to 202.96.128.68 (29 bytes)
12/18/03 17:18:01 Debug: received block [90] (server 202.96.134.133, port 53)
12/18/03 17:18:01 Debug: no information for response [1116] (server 202.96.134.133)
12/18/03 17:18:01 Debug: request [014ff62e] "pop.163.com.Omnicare.com." (no response on try 1)
12/18/03 17:18:01 Debug: multicast request [014ff62e]<2> (3 good servers)
12/18/03 17:18:01 Debug: request [014ff62e](ID 1120) sent to 202.96.128.143 (42 bytes)
12/18/03 17:18:01 Debug: request [014ff62e](ID 1121) sent to 202.96.134.133 (42 bytes)
12/18/03 17:18:01 Debug: request [014ff62e](ID 1122) sent to 192.168.1.1 (42 bytes)
12/18/03 17:18:01 Request: request [0263151e] A lookup "pop.163.com.Omnicare.com."
12/18/03 17:18:01 Debug: bounce request [0263151e]<0> to try 1 (nothing useful in cache)
12/18/03 17:18:01 Debug: selected 202.96.128.143 for request [0263151e]<1> (best looking)
12/18/03 17:18:01 Debug: request [0263151e](ID 1123) sent to 202.96.128.143 (42 bytes)
12/18/03 17:18:01 Debug: received block [90] (server 202.96.128.143, port 53)
12/18/03 17:18:01 Debug: added to cache from [014ff62e]
12/18/03 17:18:01 Debug: completed [014ff62e](ID 1120) (0.07s)
12/18/03 17:18:01 Debug: received block [90] (server 192.168.1.1, port 53)
12/18/03 17:18:01 Debug: no information for response [1117] (server 192.168.1.1)
12/18/03 17:18:01 Debug: received block [90] (server 202.96.128.143, port 53)
12/18/03 17:18:01 Debug: added to cache from [0263151e]
12/18/03 17:18:01 Debug: completed [0263151e](ID 1123) (0.08s)
12/18/03 17:18:01 Debug: received block [90] (server 192.168.1.1, port 53)
12/18/03 17:18:01 Debug: no information for response [1122] (server 192.168.1.1)
12/18/03 17:18:02 Debug: request [0263c666] "pop.163.com." (no response on try 1)
12/18/03 17:18:02 Debug: multicast request [0263c666]<2> (3 good servers)
12/18/03 17:18:02 Debug: request [0263c666](ID 1124) sent to 202.96.128.143 (29 bytes)
12/18/03 17:18:02 Debug: request [0263c666](ID 1125) sent to 202.96.134.133 (29 bytes)
12/18/03 17:18:02 Debug: request [0263c666](ID 1126) sent to 192.168.1.1 (29 bytes)
12/18/03 17:18:02 Request: request [014ff62e] A lookup "pop.163.com."
12/18/03 17:18:02 Debug: bounce request [014ff62e]<0> to try 1 (nothing useful in cache)
12/18/03 17:18:02 Debug: selected 202.96.128.143 for request [014ff62e]<1> (best looking)
12/18/03 17:18:02 Debug: request [014ff62e](ID 1127) sent to 202.96.128.143 (29 bytes)
12/18/03 17:18:02 Debug: received block [249] (server 202.96.128.143, port 53)
12/18/03 17:18:02 Debug: added to cache from [0263c666]
12/18/03 17:18:02 Debug: completed [0263c666](ID 1124) (0.07s)
12/18/03 17:18:02 Debug: received block [249] (server 202.96.128.143, port 53)
12/18/03 17:18:02 Debug: added to cache from [014ff62e]
12/18/03 17:18:02 Debug: completed [014ff62e](ID 1127) (0.08s)
12/18/03 17:18:02 Debug: received block [249] (server 192.168.1.1, port 53)
12/18/03 17:18:02 Debug: no information for response [1126] (server 192.168.1.1)
12/18/03 17:18:03 Debug: received block [281] (server 202.96.134.133, port 53)
12/18/03 17:18:03 Debug: no information for response [1125] (server 202.96.134.133)
12/18/03 17:18:03 Debug: received block [90] (server 202.96.128.68, port 53)
12/18/03 17:18:03 Debug: no information for response [1118] (server 202.96.128.68)

[kgoodknecht]

[quote="gjethro"]The problem is

The lan have a domain controller 192.168.1.10,
wingate server ip address is 192.168.0.1, 192.168.1.1 and using ADSL,
Setting for lan's pc behind the wingate server is:
the DNS setting
--192.168.1.1
--192.168.1.10
the IE setting (Use NAT)From the lan's pc behind the wingate server

Windows 2000 Domain controller?
Do not use Wingate DNS, disable it, point all internal machines including the DC to the IP of the DC ONLY for DNS.
Put a forwarder in DNS to your ISP's DNS, if the enable forwarders option is grayed out delete the "." forward lookup zone and refresh the DNS console.
In the Wingate DNS resolvers list put the IP of your DC.

Keep in mind in a Windows 2000 domain ALL DNS queries must go to the DC then let DNS on the DC resolve ALL DNS queries by using Root Hints or forwarders.

This is a major mistake I see with the way Qbik says to use Wingate on a Windows 2000 domain. DNS that comes with Wingate is nothing more than a caching DNS proxy service that relies fully on other DNS servers to resolve its DNS names. The DNS service on Win2k can resolve any name on the ICAAN Root as long as the "." zone is deleted, with out the need of your ISP's DNS. Forwarders are only optional.

Kevin D. Goodknecht [MVP]

[gjethro]

Thanks very much!!! I will try

[Rasheedat Owodeyi]

I have notice that some feature on my wingate is disabled, especially the extended network driver, only the general appears nothing else.

My DNS binding shows error, will this affect the wingate service in anyway.

A few of my computers on nAT can not found server when using MSN, do you know how i can solve this problem.

[Rasheedat Owodeyi]

is the traffice monitor suppose to be enabled on the wingate. i am trying to keep trck on my trafficc and it is disabled.

Does anyone know why this is the case here.

Why is msn messenger working on some of my systems while it is not working on the others. i have server working wiht NAT and proxy enable on the workstations

[kgoodknecht]

I have notice that some feature on my wingate is disabled, especially the extended network driver, only the general appears nothing else.

My DNS binding shows error, will this affect the wingate service in anyway.

A few of my computers on nAT can not found server when using MSN, do you know how i can solve this problem.

If the DNS binding shows an error, you would most likely have another service using port 53. This would have to be a a DNS server or another DNS proxy service, such as ICS.

A little more info on this machine will help a lot.

Kevin D. Goodknecht [Windows Server MVP]

[Rasheedat Owodeyi]

i am using window2000 server software on my server computer and i have no other software apart from wingate on the system. how do i know if there is any services making use of 53 port on my computer.

i have wingate on my server to control my internal network through the dhcp enabled on my other systems.

thanks