Local Sites list in dialer

[winstonk]

Hi:

I just upgraded to 5.2.2 from 5.0.2 -- hoping that the "Local Sites" feature of the dialer would work as advertised. However, there seems to be no change from the previous behavior (still doesn't work). I have listed both node names and IP addresses for all machines on my LAN; but if I allow DNS to initiate the dialer, TCP connection requests to a listed node within my local LAN still initiates the dialer for no good reason. So, I'm back to manual dialing -- just as before.

The knowlege base articles about spurious dialing don't really provide any applicable advice--other than to suggest using the "Local Sites" list to ignore local DNS requests--which is what I'm trying to do. Not using Samba, Telnet, FTP, TCP, etc. is not an option.

If anyone has any suggestions on how to make this feature work as the documentation suggests, I'd be extremely grateful.

Winston Kriger
Cactus Technology
Austin, TX 78750

[neil]

I take it your using NAT? Do you see "TCP connection to" in the activity screen in Gatekeeper? What does the rest say? The Local sites part of the dialer was not implemented for NAT really. It was for proxy requests only, and indeed works as it should in this regard. The Local Site feature is to block on a 'connect to' basis, hence why the proxy works. But a DNS request is not connecting to that site, rather trying to resolve where it maybe.

If you are getting something like 'TCP Connection to 192.168.0.1:137' appear in Activity, this sounds like something misconfigured somewhere. Also you could add your networks IP to the LMHOSTS file, which can be accessed through WinGate's DNS / WINS resolver.

Regards

Neil

[winstonk]

Niel sez:
"I take it your using NAT? Do you see "TCP connection to" in the activity screen in Gatekeeper? What does the rest say? "

-Yes, I'm using NAT; and No, the activity that causes my problem is logged as "DNS: A lookup .......".

Niel continues:
"The Local sites part of the dialer was not implemented for NAT really. It was for proxy requests only.............."

-Well, that explains why it doesn't work. Perhaps Qbik would consider making the "local" list apply to NAT connections in the next release (I'd really appreciate that!).

Thanx,

Winston