On Sunday 12 May 2002 6:29 pm, Kramer wrote: > Windows client hosts on the NATed LAN can't find the NT4 Domain for > logon. Therefore Network Neighborhood browsing doesn't work. > > I am sure I am not the first to run into this. Can anyone help?
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 see other machines on the same network segment, but will never see anything on the other side of a router (whether NAT is involved or not). In this case, of course, your firewall machine is a router. If you set up shares etc to specific IP addresses then your client machines should have no problem making and restoring connections, but you won't be able to browse (in Windows terminology) beyond a router. If you really *do* need to do this, I think you need to look into bridging instead of routing, in order to make the two sides of your firewall both the same network (whic=lst still keeping them separate from the Internet, of course). Unfortunately I have no experience of this, although I believe others on this list can point you in the right direction. Hope this helps, Antony.
