Accessing Samba server in DMZ
This note explains how to access a Samba server located on the “orange” DMZ subnet from a Windows PC on the “green” LAN. The problem for Samba is caused by the firewall blocking NETBIOS responses. In the firewall log you may see the following entries indicative of this issue:
13:39:07 eth1 - UDP 192.168.123.117 137(NETBIOS-NS) 192.168.123.255 137(NETBIOS-NS) 13:39:11 eth1 - UDP 192.168.123.117 138(NETBIOS-DGM) 192.168.123.255 138(NETBIOS-DGM)
In this case 192.168.123.117 is the IP of the Samba server and 192.168.123.255 is the broadcast address of the “orange” DMZ interface.
Configuration used for this example: Smoothwall firewall running on a stand-alone computer with three NICs and “red-orange-green” network profile; a SuSE Linux Samba server connected to the “orange” DMZ interface with subnet 198.168.123; a Windows XP Home PC on the “green” LAN with subnet 192.168.122. See the diagram below:
On the Windows PC go to the %SystemRoot%\System32\Drivers\Etc (i.e. C:\WINNT\system32\drivers\etc) and rename file lmhosts.sam to lmhosts
Open the lmhosts file in Notepad and add your Samba server as shown below:
192.168.123.117 deathstar #PRE #DOM:jedi 192.168.123.117 deathstar_smb #PRE #DOM:jedi
In this example 192.168.123.117 is the IP address of the Samba server on the “orange” DMZ network. Deathstar is the primary host name and deathstar_smb is samba hostname. And jedi is the domain name as displayed by `domainname` command ran on the Samba server.
Save the file, exit Notepad and click Start -> Run -> cmd -> OK -> nbtstat -R This will reload the NBT Remote Cache Name Table.
Still in the command prompt type nbtstat -c to view your current NetBIOS Remote Cache Name Table.
Popularity: 11% [?]
I use to suffer the same issue until I get my well setted up Ubuntu Box wich support...
