Message from discussion Problem with DNS Lookup behind XP Firewall

Path: g2news1.google.com!news1.google.com!proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsoutpeer00.lnd.ops.eu.uu.net!lnewsinpeer00.lnd.ops.eu.uu.net!emea.uu.net!feed1.jnfs.ja.net!feed2.jnfs.ja.net!jnfs.ja.net!gemini.csx.cam.ac.uk!news.cam.ac.uk!not-for-mail
From: "Robin Walker" <r...@cam.ac.uk>
Newsgroups: microsoft.public.windowsxp.work_remotely
Subject: Re: Problem with DNS Lookup behind XP Firewall
Date: Tue, 4 Jan 2005 18:09:19 -0000
Organization: University of Cambridge, England
Lines: 27
Message-ID: <crem4j$s2q$1@gemini.csx.cam.ac.uk>
References: <OSIqBEm8EHA.2568@TK2MSFTNGP10.phx.gbl>
NNTP-Posting-Host: qjunbur.quns.cam.ac.uk
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Response

Richard Tubb wrote:

> We've recently rolled out Windows XP SP2 to our remote users and have
> enabled the XP Firewall on all network connections, including the VPN
> connection to the main office.
>
> We are now experiencing problems wherein users can't access PC's on
> the remote domain by name, only by IP address, when connected via
> VPN. Turning off the XP Firewall for the VPN immediately solves this
> problem - so the issue appears to be with DNS lookup through the XP
> Firewall.

My guess is that this is not a DNS problem, but a NetBIOS one.  DNS lookups 
are not blocked by Windows Firewall.

Maybe you should check that the "scope" of the File & Print Sharing 
Exception in Windows Firewall includes explicitly:
(a) the subnets in use in your office LAN;
(b) the subnet ranges you allocate for VPN connections.

Do not rely on the default "My network (subnet) only" scope.

-- 
Robin Walker
r...@cam.ac.uk