On Sun, May 12, 2002 at 01:29:09PM -0400, Kramer wrote:
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.
In normal IP networks
- Original Message -
From: Kramer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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
On Tue, May 14, 2002 at 01:25:01PM -0300, Luciano Macedo Rodrigues wrote:
Hi Ray,
Changing about 10 workstations it's not always a good solution, so I found
another (great thanks to Sebastian Wolfgarten).
iptables -I INPUT -i eth1 -p UDP --sport 137 --dport 137 -j ACCEPT
iptables -I
:55
Cc: [EMAIL PROTECTED]
Assunto: Re: MS Windows domain logon via netfilter NAT
I do not see why you need to go back to win2k for firewalling.
1.- Is the domain controller on the Internet?
2.- How many machines will be accessing this server?
3.- Why do you need to NAT?
Daniel
On Mon
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.
I assume from your description that the NT4 domain controller is not on
the
same subnet as the NATted machines ?
In which case the answer is simple - Windows Networking operates using
NetBeui, which is a broadcast, non-routable protocol. Any machine
'browsing' on your local network will
Do a search at technet. There are some articles on how to get a windows client to
'find' domain masters on different subnets.
Ray
02/05/12 07:29:09, Kramer [EMAIL PROTECTED] wrote:
I have gotten a RedHat 7.3 box operating as a router/filter to a private
(192.168.132.0/24) with dhcp without
