From: "Iced Tea" <Iced_tea@gmx.net>
To: Kramer <kramer@ufl.edu>
Cc: netfilter@lists.samba.org
Subject: Re: MS Windows domain logon via netfilter NAT
Date: Mon, 13 May 2002 05:41:47 +0200 [thread overview]
Message-ID: <002501c1fa30$1ec53760$0501a8c0@lennet.de> (raw)
In-Reply-To: 3CDEA665.5040605@ufl.edu
----- Original Message -----
From: "Kramer" <kramer@ufl.edu>
To: <netfilter@lists.samba.org>
Sent: Sunday, May 12, 2002 7:29 PM
Subject: MS Windows domain logon via netfilter NAT
> I have gotten a RedHat 7.3 box operating as a router/filter to a private
> (192.168.132.0/24) with dhcp without too much trouble. One major
> problem remains that I can't find any info on. The fixes for the NAT
> public address reverse routing and the broadcast address fixes are
> already applied.
>
> Windows client hosts on the NATed LAN can't find the NT4 Domain for
> logon. Therefore Network Neighborhood browsing doesn't work. Strangely
> direct UNC connections will work if logon credentials are not required.
>
> I am sure I am not the first to run into this. Can anyone help?
>
> Jack Kramer
> University of Florida
> Fort Lauderdale
Windows usually build its browselist via broadcasting.
If the clients are not on the same network they need a domain master in each
network that knows the other network. That cannot work if the domains are
the same.
Then set up fine routing and start a wins server a machine, and all other
machines have to use wins.
works fine here, im'm migrating a network to an other ip range without
interrupting client users ...
bye
Iced_tea
prev parent reply other threads:[~2002-05-13 3:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CDEA665.5040605@ufl.edu>
2002-05-12 18:30 ` MS Windows domain logon via netfilter NAT Joerg Mayer
2002-05-13 3:41 ` Iced Tea [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002501c1fa30$1ec53760$0501a8c0@lennet.de' \
--to=iced_tea@gmx.net \
--cc=kramer@ufl.edu \
--cc=netfilter@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox