RE: FreeBSD 7.0 jail and Samba 3




OK.. if it is running inside your jail it doesnt respond to WINS
broadcasts (request for NETBIOS Names.. oi, who is Machine on this
subnet???), if it is not running in your jail, it is.

I wouldn't say "WINS broadcasts" but NetBIOS broadcasts, yes. "Machine"
is jailed Samba 3 server - I want it to be accessible from Windows machines
via \\Machine. But it is not unless I put it out of jail (or turn on WINS in
smb.conf and enter the WINS server IP into Windows clients). Windows >machines
don't have the WINS server set - I don't want to use WINS server capability
of Samba (nor of any other server on the network).

So, what are your settings for master (local, domain and wins)?

wins support = no
local master = yes
domain master = yes
preferred master = yes

can you do a ping to machine? Can it be resolved?

C:\Users\Nejko.DOMAIN>ping freebsd
Ping request could not find host freebsd. Please check the name and try >again.

C:\Users\Nejko.DOMAIN>ping 192.168.15.201



Pinging 192.168.15.201 with 32 bytes of data:
Reply from 192.168.15.201: bytes=32 time<1ms TTL=64

Can you connect smbclient //ipadres?

You mean \\192.168.15.201. Yes.

Do you see the smb client listening on the machines virtual ip?

You mean smb server - yes:

root smbd 1436 18 tcp4 192.168.15.201:445 *:*
root smbd 1436 19 tcp4 192.168.15.201:139 *:*
root nmbd 1430 6 udp4 192.168.15.201:137 *:*
root nmbd 1430 7 udp4 192.168.15.201:138 *:*
root nmbd 1430 8 udp4 192.168.15.201:137 *:*
root nmbd 1430 9 udp4 192.168.15.201:138 *:*

in case the above work for you it is all about name resolution.
# man smbclient
Read the first paragraph of servicename on servername resolution.

I know it is all about network resolution. But the question is how to
convince a jailed Samba to reply to NetBIOS broadcasts. I can't find this
in any manual.

Thanks,
Nejc

This is nota n issue with samba it is a name resolve issue.
If you add in c:\windows\system32\drivers\etc\hosts the following does all work then

ipadress Machine-name

where ipadress is the ipadres of the jailed samba server and machine-name is the netbios name of the jailed server.

If this works then you need to check your DNS server.


_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • FIXED: Not all computers see server...
    ... The NETBIOS over TCP/IP cured the problem and retained my firewall ... > domain mixed-mode network with DHCP and DNS, ... This was due to needed to connect with older machines ... After installing the server software and making the new server ...
    (microsoft.public.windows.server.networking)
  • Re: should I need WINS?
    ... You need NetBIOS if you wish to ... support EITHER legacy OS clients OR ... If you use WINS Server then EVERY machine must be ... And since you have only four machines broadcasts are ...
    (microsoft.public.windows.server.dns)
  • Re: Master Browser problem
    ... DNS and WINS server as well. ... it will use DNS to resolve DNS names and NetBIOS to resolve ... IPX should not generally be installed on your machines unless they are ...
    (microsoft.public.windows.server.general)
  • Re: Net Send or Console Message
    ... --Jonathan Maltz [Microsoft MVP - Windows Server, ... >> When I do a net send to netbios name of machine I get a 2273. ... >> Both machines have static IP's and I do not have a WINS server running ... Should I choose the 2nd option in XP for Enable NetBios over ...
    (microsoft.public.windows.server.networking)
  • Re: Network Resource Permissions
    ... NetBIOS is required on ALL machines. ... OR running on the machines so that NetBIOS is getting filtered. ... Browsing is NOT "permission" controlled until you click on an actual server ... I am able to map a drive by going to the map network drives folder, ...
    (microsoft.public.windows.server.general)