Shorewall users - Oct 2003 - OpenVPN and Ethernet Bridging

> 
> What are the Windoze versions of both the DCs and the workstations? -
> it''s important. NT4 DCs with any clients have a very different set
of
> rules for what''s needed for browsing to work properly than 
> Win2K/2K3 DCs
> with Win2K/XP clients....
Hello Greg:
One older server is an NT DC, and the two others (including the WINS server
with Active Directory, running DNS) are Win2K. Clients are Win2K or XP.
On the clients I have set the first DNS to the (internal) address of our
local DNS server. Maybe that will do it?

Thanks
--Micha
> 
> NT4 DCs of course depend on WINS and NetBIOS over TCP/IP. 
> Win2K/2K3 DCs
> with 2K+ clients depend entirely on DNS - if the client is 
> using outside
> DNS servers, he''s blind as a bat to the internal domain structure.
> 
> 
> -- 
> Greg White
> _______________________________________________
> Shorewall-users mailing list
> Post: Shorewall-users@lists.shorewall.net
> Subscribe/Unsubscribe: 
> https://lists.shorewall.net/mailman/listinfo/shorewall-users
> Support: http://www.shorewall.net/support.htm
> FAQ: http://www.shorewall.net/FAQ.htm
>

On Sat Oct 10/18/03, 2003 at 08:13:34PM +0200, Micha Silver
wrote:
> > 
> > What are the Windoze versions of both the DCs and the workstations? -
> > it''s important. NT4 DCs with any clients have a very
different set of
> > rules for what''s needed for browsing to work properly than 
> > Win2K/2K3 DCs
> > with Win2K/XP clients....
> 
> Hello Greg:
> One older server is an NT DC, and the two others (including the WINS server
> with Active Directory, running DNS) are Win2K. Clients are Win2K or XP.
> On the clients I have set the first DNS to the (internal) address of our
> local DNS server. Maybe that will do it?
If by "local" you mean the Win2K/AD/DNS server, then yep, that ought
to
do it. Was this _not_ the case before, and you''ve just set it now? If
so, it ought to resolve your problem. If not, ensure that DNS is working
properly on the client. Try:

nslookup
> set type=any
> <domain.name>
where <domain.name> is the DNS name of your AD domain.
It should dump out a ton of info, including IP addresses, NS records,
etc.

If _that_ works, and browsing does still not work, ensure that clients
can reach TCP/445 and TCP/135-137-138-139.

We''re getting a bit OT here for this list. :)

-- 
Greg White