[Samba] NetBIOS called name not sent using smbclient 4.0.9 and CUPS 1.6.3
I suspect a bug in either smbclient 4.0.9 or CUPS 1.6.3 (which wouldn't be Samba's problem, of course) where a linux client does not send the server's Called Name in the NetBIOS session request sent to a server using smb. Now, the problem is that my university's print system selects the print configuration file to use based on matching the Called Name. No Called Name leads to no configuration and no printing. Attached are two packet captures for access to the same print server from two different machines. One session, capture-printsmb-ubuntu-filtered.pcap, clearly sends PRINTSMB.SCIENC as Called Name (packet 10). This is using CUPS 1.6.2 and smbclient 3.6.9 on an Ubuntu 13.04 installation. The other session, capture-printsmb-1-filtered.pcap, has an empty field (repeating bytes 0xCA) at that location. This is using CUPS 1.6.3 and smbclient 4.0.9 on an (up-to-date) Arch linux installation. The DeviceURI used for this printer is smb://username:password@science/printsmb.science.ru.nl/lazarus The server's administrators and I have established (and it can be seen in the packet captures) that the machine is being reached, and that the only difference really is with the NetBIOS session request. Now, either the problem is with CUPS, or rather, how CUPS calls smbclient and what information is passed along, or it is with smbclient itself. Because of this, I'm also sending this e-mail to the OSX Printing List (because the CUPS lists themselves are down right now), and hope we can reach a conclusion of why this is happening, and whether it should be fixed. Regards, Pol Van Aubel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] NetBIOS browsing
Hello: why an ubuntu 12.04 machine with samba3 joined to my samba AD domain can be seen in network neighborhood and not my debian 6 with samba3? Best regards, Felix. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
This is right. Openvpn does the job perfectly fine here connecting our far away office in our network and Samba-Domain. --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Ben Metcalfe Gesendet: Montag, 9. Juli 2012 01:35 Cc: samba@lists.samba.org Betreff: Re: [Samba] Netbios over VPN Additionally on Sebastian's point: http://openvpn.net/index.php/open-source/faq/75-general/293-what-is-the-prin ciple-behind-openvpn-tunnels.html People who are running applications that need the special features of ethernet (which won't work on an IP-only network) will often bridge their physical local ethernet with a tap device (using a utility such as brctl on Linux), then VPN the tap device to another similar setup at the other end. This allows OpenVPN to route ethernet broadcasts and non-IP protocols such as Windows NetBios over the VPN... -Ben. On 8 July 2012 23:27, Bob Miller b...@computerisms.ca wrote: Hello, I believe you can use WINS to solve this problem. It's been a while, my neurons may be rusty, but I had a similar set up using openswan. I believe winbind will do what you want; configure samba to use winbind and your road warriors with that as their wins server. If I remember correctly, the road warriors will register with the winbind server, then everyone on the network configured to use the winbind server should be able to find them... Check here for better information (or at least a place to start): http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrow sing.html#id2585378 On Thu, 2012-07-05 at 10:30 -0400, Andrew Mark wrote: I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca b...@computerisms.ca Network, Internet, Server, and Open Source Solutions -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
maybe because the name : john_laptop is not RFC. try changing it to : john-laptop and test again. read : http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names in short : While a hostname may not contain other characters, such as the underscore character (_), other DNS names may contain the underscore.[2] Systems such as DomainKeys and service records use the underscore as a means to assure that their special character is not confused with hostnames Louis -Oorspronkelijk bericht- Van: andr...@aimsystems.ca [mailto:samba-boun...@lists.samba.org] Namens Andrew Mark Verzonden: 2012-07-05 16:30 Aan: samba@lists.samba.org Onderwerp: [Samba] Netbios over VPN I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
Am Montag, 9. Juli 2012, 08:29:00 schrieb Daniel Müller: This is right. Openvpn does the job perfectly fine here connecting our far away office in our network and Samba-Domain. We can recommend OpenVPN too. The easiest way to connect to a Samba by VPN in the majority of scenarios should be the OpenVPN TAP mode (layer 2) - but security may more difficult to handle a bit. - see i.e.: http://openvpn.net/index.php/open-source/documentation/howto.html#samba for some basics about this... To solve name resolution questions i knew manies who are using a DNS with their samba / OpenVPN setup. Not shure how far samba / windows network browsing is working today over tap correctly (did not tried that in the past again) but may be there are more clever solutions possible today. hth best regards, Niels. -- --- Niels Dettenbach Syndicat IT Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- signature.asc Description: This is a digitally signed message part. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
Niels Dettenbach n...@syndicat.com escreveu: Am Montag, 9. Juli 2012, 08:29:00 schrieb Daniel Müller: This is right. Openvpn does the job perfectly fine here connecting our far away office in our network and Samba-Domain. We can recommend OpenVPN too. The easiest way to connect to a Samba by VPN in the majority of scenarios should be the OpenVPN TAP mode (layer 2) - but security may more difficult to handle a bit. - see i.e.: http://openvpn.net/index.php/open-source/documentation/howto.html#samba for some basics about this... To solve name resolution questions i knew manies who are using a DNS with their samba / OpenVPN setup. Not shure how far samba / windows network browsing is working today over tap correctly (did not tried that in the past again) but may be there are more clever solutions possible today. hth best regards, Niels. -- --- Niels Dettenbach Syndicat IT Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Hi there, We are using tun (routed) without problems. Just a matter of configuring wins and/or dns. []s, Fernando Lozano -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
did you have the dns service enabled? 2012/7/5 Andrew Mark andr...@aimsystems.ca: I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
Am 05.07.2012 16:30, schrieb Andrew Mark: I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba [...] I presume, you're using one or more TUN device(s) on OpenVPN? If so, I recommend switching to TAP devices instead, if possible. Bridging should save you from a lot of trouble around NetBIOS/SMB. Best Regards, Sebastian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
Hello, I believe you can use WINS to solve this problem. It's been a while, my neurons may be rusty, but I had a similar set up using openswan. I believe winbind will do what you want; configure samba to use winbind and your road warriors with that as their wins server. If I remember correctly, the road warriors will register with the winbind server, then everyone on the network configured to use the winbind server should be able to find them... Check here for better information (or at least a place to start): http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id2585378 On Thu, 2012-07-05 at 10:30 -0400, Andrew Mark wrote: I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca b...@computerisms.ca Network, Internet, Server, and Open Source Solutions -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Netbios over VPN
Additionally on Sebastian's point: http://openvpn.net/index.php/open-source/faq/75-general/293-what-is-the-principle-behind-openvpn-tunnels.html People who are running applications that need the special features of ethernet (which won't work on an IP-only network) will often bridge their physical local ethernet with a tap device (using a utility such as brctl on Linux), then VPN the tap device to another similar setup at the other end. This allows OpenVPN to route ethernet broadcasts and non-IP protocols such as Windows NetBios over the VPN... -Ben. On 8 July 2012 23:27, Bob Miller b...@computerisms.ca wrote: Hello, I believe you can use WINS to solve this problem. It's been a while, my neurons may be rusty, but I had a similar set up using openswan. I believe winbind will do what you want; configure samba to use winbind and your road warriors with that as their wins server. If I remember correctly, the road warriors will register with the winbind server, then everyone on the network configured to use the winbind server should be able to find them... Check here for better information (or at least a place to start): http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id2585378 On Thu, 2012-07-05 at 10:30 -0400, Andrew Mark wrote: I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca b...@computerisms.ca Network, Internet, Server, and Open Source Solutions -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Netbios over VPN
I am attempting to utilize BackupPC on a Fedora 14 server to backup a remote client. As I understand, it's primary mechanism for finding clients is performing a nmblookup clientname This works fine for computers connected to the local network. My issue is extending ?Samba's? search to encompass our other network - the point-to-point VPNs Using OpenVPN, we have a number of road warriors who connect their VPN to gain access to the samba server. Each has a unique static IP address in the 10.30.251 range and when connected, I can find them but not samba i.e. # ping john_laptop --- john.inspirah.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 9.900/14.764/24.388/6.805 ms # nmblookup john_laptop querying john_laptop on 127.255.255.255 querying john_laptop on 10.30.7.255 name_query failed to find name john_laptop How to I configure Samba or whatever Linux service is necessary to query the 10.30.251.255 network as well -- Cheers, Andrew Mark | Development Analyst | www.aimsystems.ca local: 519-837-1072 | fax: 519-837-4063 | int'l 800-465-2961 12-350 Speedvale Ave. W. | Guelph, ON | N1H 7M7 | Canada -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] netbios uses incorrect broadcast value and termintaes
On 18 August 2010 19:58, Yatish Jain ytsh.j...@gmail.com wrote: [...] [2010/08/18 08:42:17.539962, 2] nmbd/nmbd.c:890(main) Becoming a daemon. [2010/08/18 08:42:17.567091, 2] lib/interface.c:340(add_interface) added interface en0 ip=10.209.86.7 bcast=*10.209.87.239* netmask= [...] bash-3.00# ifconfig -a en0: [...] inet 10.209.86.7 netmask 0xfc00 broadcast 10.209.87.255 [...] The difference between 10.209.87.239 and 10.209.87.255 is a single bit. Is there any possibility of bad RAM or a bit flipped by a cosmic ray in your disk cache or something? :) -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] netbios uses incorrect broadcast value and termintaes
Hi All, I am using samba Version 3.5.4 on AIX 6.1. The installation is through pware binary ( pware53.samba.rte 3.5.4.0). There seems to be a strange issue with NetBios where it terminates with the following error logged just after starting. The diagnosis fails in step 4 of Samba Diagnosis test (nmblookup -B BIGSERVER __SAMBA_) because no netbios (nmbd) is running. snippet from nmbd logs: [2010/08/18 08:42:17, 0] nmbd/nmbd.c:857(main) nmbd version 3.5.4 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2010/08/18 08:42:17.538633, 2] lib/tallocmsg.c:106(register_msg_pool_usage) Registered MSG_REQ_POOL_USAGE [2010/08/18 08:42:17.538669, 2] lib/dmallocmsg.c:77(register_dmalloc_msgs) Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED rlimit_max: rlimit_max (2048) below minimum Windows limit (16384) [2010/08/18 08:42:17.539962, 2] nmbd/nmbd.c:890(main) Becoming a daemon. [2010/08/18 08:42:17.567091, 2] lib/interface.c:340(add_interface) added interface en0 ip=10.209.86.7 bcast=*10.209.87.239* netmask= [2010/08/18 08:42:17.567158, 2] lib/interface.c:340(add_interface) added interface lo0 ip=127.0.0.1 bcast=127.255.255.255 netmask= [2010/08/18 08:42:17.567208, 2] nmbd/nmbd_subnetdb.c:299(create_subnets) create_subnets: Ignoring loopback interface. [2010/08/18 08:42:17.567289, 0] lib/util_sock.c:875(open_socket_in) bind failed on port 137 socket_addr = 10.209.87.239. Error = Can't assign requested address [2010/08/18 08:42:17.567524, 0] nmbd/nmbd_subnetdb.c:118(make_subnet) nmbd_subnetdb:make_subnet() Failed to open nmb bcast socket on interface 10.209.87.239 for port 137. Error was Can't assign requested address [2010/08/18 08:42:17.567682, 0] nmbd/nmbd.c:963(main) ERROR: Failed when creating subnet lists. Exiting. The address 10.209.87.239 is nowhere present on my system. Here is the output of ifconfig -a: bash-3.00# ifconfig -a en0: flags=5e080863,c0UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN inet 10.209.86.7 netmask 0xfc00 broadcast 10.209.87.255 tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0 lo0: flags=e08084bUP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT inet 127.0.0.1 netmask 0xff00 broadcast 127.255.255.255 inet6 ::1/0 tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1 And here is my smb.conf file: bash-3.00# testparm Load smb config files from /opt/pware/lib/smb.conf rlimit_max: rlimit_max (2000) below minimum Windows limit (16384) Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] server string = SAMBA allow trusted domains = No map to guest = Bad User passdb backend = smbpasswd log level = 2 passdb:3 auth:3 winbind:3 log file = /var/log/samba/log.%m load printers = No printcap name = /dev/null disable spoolss = Yes local master = No domain master = No ldap idmap suffix = ou=cifsidmap idmap backend = idmap_rid:WORKGROUP=1-2 idmap uid = 1-2 idmap gid = 1-2 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes kernel change notify = No dos filemode = Yes netbios name = test_nmb Please help in nailing down the issue. Regards, Yatish -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] netbios name
I discovered a strange behaviour (bug ?) with Samba and Windows explorer.exe. I explain it here in the hope it will be usefull to others. Tested with: Samba 3.2.5 from Debian Lenny Windows XP Pro and Windows 2003 into a workgroup If we disable netbios daemon *and* we set a netbios name (every other parameters left unchanged from orginal file): netbios name = whatever disable netbios = yes then we get this: - from smbclient, everything is OK - from the Windows commande line, everything is ok example: net use H: \\mysambaserver\myshare /user:sambauser - from the Windows GUI (explorer.exe) it is impossible to access to Samba shares 1 - logon to your Windows box with user windowsuser 2 - open explorer 3 - type \\mysambaserver in the address bar 4 - Windows asks for a username and password 5 - type sambauser then the password 6 - an error message states about the fact you taped a wrong password or the ressource is not reachable I digged into the detailled logs and found explorer don't send the correct username sambauser. It only send windowsuser. If we have the same username *and* password on your Windows box and on Samba, we don't see the problem. Removing netbios name solve the problem. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Netbios : Network Browsing on multiple subnets
Hi all ! I have a PDC and a BDC in 2 differents subnets. I would like to sync their browse list but it doesn't seem to work. Actually here are a part my smb.conf files : PDC -- ... remote browse sync = 10.10.20.10 remote announce = 10.10.20.10 security = user encrypt passwords = true domain logons = Yes os level = 70 preferred master = yes domain master = yes local master = yes wins support = Yes ... --- BDC ... remote announce = 10.10.10.1 remote browse sync = 10.10.10.1 wins support = yes security = user encrypt passwords = yes domain logons = Yes os level = 69 preferred master =no domain master = no ... --- The BDC is unable to find the Domain Master Browser nmblookup -U venise -R 'DOMAIN#1B' ... name_query failed to find name domain#1b nmblookup -U BDC -S PDC name_query failed to find name PDC log.nmbd --- [2008/11/14 11:55:51, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name DOMAIN1b for the workgroup DOMAIN. ... [2008/11/14 12:03:59, 0] nmbd/nmbd_incomingdgrams.c:process_master_browser_announce(383) process_master_browser_announce: Not configured as domain master - ignoring master announce. I really need help, the BDC has to be moved in another place. Thank you ! Smaine -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios : Network Browsing on multiple subnets
Scott Lovenberg wrote: [EMAIL PROTECTED] wrote: Hi all ! I have a PDC and a BDC in 2 differents subnets. I would like to sync their browse list but it doesn't seem to work. Actually here are a part my smb.conf files : PDC -- ... remote browse sync = 10.10.20.10 remote announce = 10.10.20.10 security = user encrypt passwords = true domain logons = Yes os level = 70 preferred master = yes domain master = yes local master = yes wins support = Yes ... --- BDC ... remote announce = 10.10.10.1 remote browse sync = 10.10.10.1 wins support = yes security = user encrypt passwords = yes domain logons = Yes os level = 69 preferred master =no domain master = no ... --- The BDC is unable to find the Domain Master Browser nmblookup -U venise -R 'DOMAIN#1B' ... name_query failed to find name domain#1b nmblookup -U BDC -S PDC name_query failed to find name PDC log.nmbd --- [2008/11/14 11:55:51, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name DOMAIN1b for the workgroup DOMAIN. ... [2008/11/14 12:03:59, 0] nmbd/nmbd_incomingdgrams.c:process_master_browser_announce(383) process_master_browser_announce: Not configured as domain master - ignoring master announce. I really need help, the BDC has to be moved in another place. Thank you ! Smaine I believe you want the 'wins server =' and/or 'wins proxy' settings instead of the 'wins support' setting. Table of wins settings from Using Samba, ch07 http://de4.samba.org/samba/docs/using_samba/ch07.html#samba2-CHP-7-TABLE-1 The entry on 'wins server =' and 'wins proxy' is just under this table. Unless I'm mistaken, wins proxy/wins server combination is the only one that will allow cross subnet wins replication (other than DNS/LDAP combination). IIRC, you'll want the wins servers to be master browsers on their respective subnets, as well. Sorry, I realized right after posting that last sentence might not have been clear; I meant each should be the local master browser. A domain can only have one domain master browser. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios : Network Browsing on multiple subnets
[EMAIL PROTECTED] wrote: Hi all ! I have a PDC and a BDC in 2 differents subnets. I would like to sync their browse list but it doesn't seem to work. Actually here are a part my smb.conf files : PDC -- ... remote browse sync = 10.10.20.10 remote announce = 10.10.20.10 security = user encrypt passwords = true domain logons = Yes os level = 70 preferred master = yes domain master = yes local master = yes wins support = Yes ... --- BDC ... remote announce = 10.10.10.1 remote browse sync = 10.10.10.1 wins support = yes security = user encrypt passwords = yes domain logons = Yes os level = 69 preferred master =no domain master = no ... --- The BDC is unable to find the Domain Master Browser nmblookup -U venise -R 'DOMAIN#1B' ... name_query failed to find name domain#1b nmblookup -U BDC -S PDC name_query failed to find name PDC log.nmbd --- [2008/11/14 11:55:51, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name DOMAIN1b for the workgroup DOMAIN. ... [2008/11/14 12:03:59, 0] nmbd/nmbd_incomingdgrams.c:process_master_browser_announce(383) process_master_browser_announce: Not configured as domain master - ignoring master announce. I really need help, the BDC has to be moved in another place. Thank you ! Smaine I believe you want the 'wins server =' and/or 'wins proxy' settings instead of the 'wins support' setting. Table of wins settings from Using Samba, ch07 http://de4.samba.org/samba/docs/using_samba/ch07.html#samba2-CHP-7-TABLE-1 The entry on 'wins server =' and 'wins proxy' is just under this table. Unless I'm mistaken, wins proxy/wins server combination is the only one that will allow cross subnet wins replication (other than DNS/LDAP combination). IIRC, you'll want the wins servers to be master browsers on their respective subnets, as well. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS Hostname
I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct However, (Design Flaw) at that point there was no way for me to back out or cancel, so the deed was done. How or where do you remove or change that option...? Performance Technology Systems Design Being in Politics is like being a football coach. You have to be smart enough to understand the game, and dumb enough to think it's important. Eugene McCarthy (1916 - 2005) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS Hostname
On Fri, May 30, 2008 at 1:54 PM, William W. Hammond [EMAIL PROTECTED] wrote: I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. While this may be a question better suited to the OpenSUSE list than this one, you entered a NetBIOS hostname where? In YaST? A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct What clients are no longer be able to connect? Samba clients? Or some other clients? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS Hostname
At 11:10 AM 5/30/2008, Rob Shinn wrote: On Fri, May 30, 2008 at 1:54 PM, William W. Hammond mailto:[EMAIL PROTECTED][EMAIL PROTECTED] wrote: I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. While this may be a question better suited to the OpenSUSE list than this one, you entered a NetBIOS hostname where? In YaST? Since it was a SAMBA Issue I thought this would be the best place, but if you think the OpenSuSE Forum is a better option I'll move the thread there. and, yes, it was through YaST... A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct What clients are no longer be able to connect? Samba clients? Or some other clients? Sorry, not a complete description of the problem. It was the Windows XP Clients that could no longer authenticate to a share or even the Workgroup Computer. What I needed to know was how to undue that option, or how to set up the Windows Client to use the NetBIOS name. I was under a time constraint, small system so at the time it was easier just to reinstall the O/S (now working) and learn about this later... Performance Technology Systems Design Never Promise more than you can deliver... Always Deliver more than you promise.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS Hostname
On Friday 30 May 2008 12:54:33 William W. Hammond wrote: I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct However, (Design Flaw) at that point there was no way for me to back out or cancel, so the deed was done. The issue is not whether or not Samba has a NetBIOS name, but rather that a change of the NetBIOS name will generate a new SID for the system. If that system is a PDC, you will end up with a new Domain SID, and hence your Windows clients will no longer belong to the same domain your PDC is now in. How or where do you remove or change that option...? You can find out the original domain SID from your Samba log files in /var/log/samba. Then reset the domain SID using: a) Stop Samba b) Execute: net setlocalsid S-1-5-21--xx-xxx c) Restart Samba That should restore things so long as you have not messed around with things too much, in which case it would be easier to rejoin your Windows clients to the current Samba domain setup. PS: By default Samba finds the hostname of the system it is running on and uses that to generate the machine SID (and the domain SID if it is a PDC). - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS Hostname
At 12:14 PM 5/30/2008, John H Terpstra wrote: On Friday 30 May 2008 12:54:33 William W. Hammond wrote: I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct However, (Design Flaw) at that point there was no way for me to back out or cancel, so the deed was done. The issue is not whether or not Samba has a NetBIOS name, but rather that a change of the NetBIOS name will generate a new SID for the system. If that system is a PDC, you will end up with a new Domain SID, and hence your Windows clients will no longer belong to the same domain your PDC is now in. How or where do you remove or change that option...? You can find out the original domain SID from your Samba log files in /var/log/samba. Then reset the domain SID using: a) Stop Samba b) Execute: net setlocalsid S-1-5-21--xx-xxx c) Restart Samba That should restore things so long as you have not messed around with things too much, in which case it would be easier to rejoin your Windows clients to the current Samba domain setup. Thanks, that is what I needed, goes in my Tech Save box... I still think I should have been able to opt out once I saw the warning, Is that a Samba Issue or an OpenSuSE YaST issue...? PS: By default Samba finds the hostname of the system it is running on and uses that to generate the machine SID (and the domain SID if it is a PDC). - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Performance Technology Systems Design Never Promise more than you can deliver... Always Deliver more than you promise.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS Hostname
Definitely an OpenSUSE issue. That's a really terrible GUI design. On Fri, May 30, 2008 at 3:48 PM, William W. Hammond [EMAIL PROTECTED] wrote: At 12:14 PM 5/30/2008, John H Terpstra wrote: On Friday 30 May 2008 12:54:33 William W. Hammond wrote: I was setting up Samba on an OpenSuSE 10.3 i386 computer. At the last minute I decided to enter a NetBIOS Hostname, big mistake. A message popped up warning me that entering a NetBIOS Hostname would create a new UID and Clients may no longer be able to connect. The Message was correct However, (Design Flaw) at that point there was no way for me to back out or cancel, so the deed was done. The issue is not whether or not Samba has a NetBIOS name, but rather that a change of the NetBIOS name will generate a new SID for the system. If that system is a PDC, you will end up with a new Domain SID, and hence your Windows clients will no longer belong to the same domain your PDC is now in. How or where do you remove or change that option...? You can find out the original domain SID from your Samba log files in /var/log/samba. Then reset the domain SID using: a) Stop Samba b) Execute: net setlocalsid S-1-5-21--xx-xxx c) Restart Samba That should restore things so long as you have not messed around with things too much, in which case it would be easier to rejoin your Windows clients to the current Samba domain setup. Thanks, that is what I needed, goes in my Tech Save box... I still think I should have been able to opt out once I saw the warning, Is that a Samba Issue or an OpenSuSE YaST issue...? PS: By default Samba finds the hostname of the system it is running on and uses that to generate the machine SID (and the domain SID if it is a PDC). - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Performance Technology Systems Design Never Promise more than you can deliver... Always Deliver more than you promise.. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBIOS name resolution from Linux
Wow, i was gone this weekend, heavy discussion here on this subject. What i did to make resolving work for my PDC and all of my other server my goals where, and i think this is good to know for others. 1) my pdc is my master server, 2) my email server must also resolve my pc names 3) my proxy server also must resolve my pc names 4) i must be able to resolve pcnames over wan 5) i must have dns backup. so what i came back with. 1a) samba (PDC), with dhcp and DDns. preferred master = Yes domain master = Yes os level = 65 these are used to make sure samba is master browser. dns proxy = yes this is used to make sure samba resolves over DNS first. wins support = Yes you want it to work, netbios.. so enable this. 1b) resolve.conf search yourlocaldomain.internal.local otherdomain.com ( search = to make sure my own domain is resolved first ) nameserver 127.0.0.1 other extra for internet backup ( has nothing to do with netbios resolution ) 1c) setup DHCP3 + DDNS this is done so every pc which is connected to the network and gets dhcp ip also gets recorded in the dns server. 2) my email server has a dns slave setup. i also have 1b in this server. 3) see 2 ;-) 4) i also manual record the dns of my pc's on other offices ( there are 4-5 pc's there in 2 remote offices) yes, dhcp relay should be better, but i never tried it to set it up. 5) because all of my server have the same dns setup is good to have fallback. so i think the above is a lot of crap, but i hope it helps someone. for me this setup is working sinds 2005, and im happy with it. ... as is my boss... grin.. ow and you better not uses hosts files, and dont forget to check also your nss.conf if your using ldap. Louis p.s. if i can improve some thing, please let me know. for example howto setup the dhcp relay. ;-) -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens John H Terpstra Verzonden: zaterdag 17 mei 2008 14:26 Aan: samba@lists.samba.org Onderwerp: Re: [Samba] NetBIOS name resolution from Linux On Saturday 17 May 2008 06:41:08 am Olivier Parisy wrote: John H Terpstra a écrit : On Friday 16 May 2008 09:22:43 am Charles Marcus wrote: On 5/16/2008 10:08 AM, L.P.H. van Belle wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... First why use open dns servers. the dns servers of your provider is much less hops away. Hops really don't matter... most ISP DNS servers are unreliable... some are extremely unreliable... I said 'random' meaning, it really wouldn't matter what ISP you were using, I'd say the same thing... OK - now that we have split the atom regarding what might be the best DNS solution, how does this help resolve NetBIOS names within Linux? Have I missed something vital in this thread? Seems I must have. I'd like to know how you propose to store the name_type info in DNS? For example, how would you store MYSERVERNAME20 in DNS? Next, how will you teach the Windows client to search DNS for that info. After all, we are dealing with the NetBIOS name space. With all due respect, that is not clear to me either. I am only looking for a simple way to resolve NetBIOS names on a Linux machine. Replacing NetBIOS resolution by a full-fledged local DNS would, I suppose, be appropriate on an enterprise-scale network, but we are just talking about an home LAN here (which I should have stated more clearly from the start). I am a little lost at to what the problem is here. WINS does not require winbindd to be running. On the Linux system it requires: 1) In your /etc/nsswitch.conf file: ... hosts: files wins [NOTFOUND=return] dns ... 2) Install the samba file libnss_wins.so.2 in the /lib directory (or on 64-bit systems in the /lib64 directory) 3) Run nmbd That's it! What is so difficult? What makes this so complicated? If you do not need DNS, then don't even run it (or else just run a caching DNS server). Winbind is orthogonal to wins. They serve entirely differing purposes. - John T. My understanding is the following: I need to bridge NetBIOS name resolution, as provided by nmbd, with the libc gethostbyname() standard call. The Name Service Switch (NSS) seems to be designed for this purpose: by adding a wins entry in nsswitch.conf and installing winbind, the later can then act as a service to NSS (through /lib/libnss_wins.so.2; or is it /lib/libnss_winbind.so.2?). Now, all of this is nice and dandy, but installing winbind opens a whole can of worms for me: since it also insists in handling my users and groups (which, as I understand it, is its
Re: [Samba] NetBIOS name resolution from Linux
On 5/19/2008, L.P.H. van Belle ([EMAIL PROTECTED]) wrote: 1c) setup DHCP3 + DDNS this is done so every pc which is connected to the network and gets dhcp ip also gets recorded in the dns server. What did you use for DNS? Bind? How is it configured (caching only with forwarders?) -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBIOS name resolution from Linux
Hi, i used Bind9 ( with dhcp3), with caching dns with forwarders. i have 4 local zones. these are in the resolve.conf as search domains. ( 4 different subnets ) If you want a copy of my config its possible. Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Charles Marcus Verzonden: maandag 19 mei 2008 12:56 Aan: samba@lists.samba.org Onderwerp: Re: [Samba] NetBIOS name resolution from Linux On 5/19/2008, L.P.H. van Belle ([EMAIL PROTECTED]) wrote: 1c) setup DHCP3 + DDNS this is done so every pc which is connected to the network and gets dhcp ip also gets recorded in the dns server. What did you use for DNS? Bind? How is it configured (caching only with forwarders?) -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Monday 19 May 2008, L.P.H. van Belle wrote: dns proxy = yes this is used to make sure samba resolves over DNS first. The default is yes for that parameter but your explanation doesn't fit with the man page. It doesn't use DNS first it only uses it for unregistered names, therefore it must check the WINS database first. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
John H Terpstra a écrit : On Friday 16 May 2008 09:22:43 am Charles Marcus wrote: On 5/16/2008 10:08 AM, L.P.H. van Belle wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... First why use open dns servers. the dns servers of your provider is much less hops away. Hops really don't matter... most ISP DNS servers are unreliable... some are extremely unreliable... I said 'random' meaning, it really wouldn't matter what ISP you were using, I'd say the same thing... OK - now that we have split the atom regarding what might be the best DNS solution, how does this help resolve NetBIOS names within Linux? Have I missed something vital in this thread? Seems I must have. I'd like to know how you propose to store the name_type info in DNS? For example, how would you store MYSERVERNAME20 in DNS? Next, how will you teach the Windows client to search DNS for that info. After all, we are dealing with the NetBIOS name space. With all due respect, that is not clear to me either. I am only looking for a simple way to resolve NetBIOS names on a Linux machine. Replacing NetBIOS resolution by a full-fledged local DNS would, I suppose, be appropriate on an enterprise-scale network, but we are just talking about an home LAN here (which I should have stated more clearly from the start). My understanding is the following: I need to bridge NetBIOS name resolution, as provided by nmbd, with the libc gethostbyname() standard call. The Name Service Switch (NSS) seems to be designed for this purpose: by adding a wins entry in nsswitch.conf and installing winbind, the later can then act as a service to NSS (through /lib/libnss_wins.so.2; or is it /lib/libnss_winbind.so.2?). Now, all of this is nice and dandy, but installing winbind opens a whole can of worms for me: since it also insists in handling my users and groups (which, as I understand it, is its primary goal after all), it cannot work out of the box and breaks my simple SMB share setting. So I would say that winbind (or the fact that winbind + libnss_wins.so are distributed as the same packet on Debian?) is overkill for me. Is this description correct? I'd be very interested in a confirmation. Regards. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
Chris Smith a écrit : A few thoughts, take from them what you will (and remember, free advice is worth what you pay for it). That is understandable. Thanks for your time :-) It's really good to have proper IP name resolution. Requires DNS or (ugh) hosts files. It can also be good to have NetBIOS name resolution, if you have the need (Windows type browsing and sharing in non-native AD environments). Implies WINS or (ugh) lmhosts files for resolution (or you're left only with broadcasts). Yes, that is what I would like to achieve, and without static settings as much as possible. I am actually mostly interested in NetBIOS names resolutions (all my computers use Windows or Linux + Samba); that LAN worked without a DNS until now, and I would like to keep it that way. It's good to avoid security=share, especially if you want to run WINS. I understand this. But that is simpler, and enough for me. That share is only used by local, trusted computers. And yes, a proper setup using security=user can provide guest shares. I suppose so. But as described in my previous answers, everything is already working flawlessly, excepted the Linux NetBIOS name resolution. So I would like to avoid changing all my setting just for solving this, if at all possible. Winbind is normally used to authenticate against Windows servers that are running WINS or AD, so that you don't need to duplicate the Windows user/groups. I think that is the crux of the matter. I am definitely not interested in this functionality of winbind, which seems to impose a modification of all my setup; all I am interested in is the name resolution part (for which a bridging through the Name Service Switch seems reasonable). By the way, people on #samba seemed surprised by the fact that I needed to install the winbind packet to gain access to ls /lib/lib_wins.so.2. Is this the same with other distributions (I am using Debian Etch)?. Is there as an example a way I could compile and install only this library, without winbind? You don't mention how big your network is, but if you're dealing with 5 or more systems I highly suggest both DNS and WINS over their static equivalents, hosts and lmhosts, respectively. Even with fewer systems, it can be a good idea to bother with the setup if you intend to grow or want flexibility. I should have definitely stated this from the start. My setting is the following: a Windows host embedding a Debian virtual machine. Both get Internet connectivity and IP addresses through the DHCP server of a small xDSL routing box. I am interested in NetBIOS resolution so that the virtual machine could more easily get the Windows host IP (remember that this is a dynamic setting). So yes, I could hardcode everything or, at the opposite of the scale, install a full DNS and WINS solution. But I expected a simpler, more flexible solution could be found inbetween. Regards, Olivier Parisy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Saturday 17 May 2008 06:41:08 am Olivier Parisy wrote: John H Terpstra a écrit : On Friday 16 May 2008 09:22:43 am Charles Marcus wrote: On 5/16/2008 10:08 AM, L.P.H. van Belle wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... First why use open dns servers. the dns servers of your provider is much less hops away. Hops really don't matter... most ISP DNS servers are unreliable... some are extremely unreliable... I said 'random' meaning, it really wouldn't matter what ISP you were using, I'd say the same thing... OK - now that we have split the atom regarding what might be the best DNS solution, how does this help resolve NetBIOS names within Linux? Have I missed something vital in this thread? Seems I must have. I'd like to know how you propose to store the name_type info in DNS? For example, how would you store MYSERVERNAME20 in DNS? Next, how will you teach the Windows client to search DNS for that info. After all, we are dealing with the NetBIOS name space. With all due respect, that is not clear to me either. I am only looking for a simple way to resolve NetBIOS names on a Linux machine. Replacing NetBIOS resolution by a full-fledged local DNS would, I suppose, be appropriate on an enterprise-scale network, but we are just talking about an home LAN here (which I should have stated more clearly from the start). I am a little lost at to what the problem is here. WINS does not require winbindd to be running. On the Linux system it requires: 1) In your /etc/nsswitch.conf file: ... hosts: files wins [NOTFOUND=return] dns ... 2) Install the samba file libnss_wins.so.2 in the /lib directory (or on 64-bit systems in the /lib64 directory) 3) Run nmbd That's it! What is so difficult? What makes this so complicated? If you do not need DNS, then don't even run it (or else just run a caching DNS server). Winbind is orthogonal to wins. They serve entirely differing purposes. - John T. My understanding is the following: I need to bridge NetBIOS name resolution, as provided by nmbd, with the libc gethostbyname() standard call. The Name Service Switch (NSS) seems to be designed for this purpose: by adding a wins entry in nsswitch.conf and installing winbind, the later can then act as a service to NSS (through /lib/libnss_wins.so.2; or is it /lib/libnss_winbind.so.2?). Now, all of this is nice and dandy, but installing winbind opens a whole can of worms for me: since it also insists in handling my users and groups (which, as I understand it, is its primary goal after all), it cannot work out of the box and breaks my simple SMB share setting. So I would say that winbind (or the fact that winbind + libnss_wins.so are distributed as the same packet on Debian?) is overkill for me. Is this description correct? I'd be very interested in a confirmation. Regards. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
John H Terpstra a écrit : I am a little lost at to what the problem is here. WINS does not require winbindd to be running. On the Linux system it requires: 1) In your /etc/nsswitch.conf file: ... hosts: files wins [NOTFOUND=return] dns ... 2) Install the samba file libnss_wins.so.2 in the /lib directory (or on 64-bit systems in the /lib64 directory) 3) Run nmbd That's it! What is so difficult? What makes this so complicated? If you do not need DNS, then don't even run it (or else just run a caching DNS server). Winbind is orthogonal to wins. They serve entirely differing purposes. Ah, thank you! That is exactly what I expected. I am pleased to read that winbind and wins are different beasts, as I have no interest in the former. The point is that, under Debian, the /lib/libnss_wins.so.2 file is distributed only in the winbind package, as confirmed by this search: http://packages.debian.org/search?searchon=contentskeywords=libnss_winsmode=filenamesuite=stablearch=any So it seems like this is a packaging issue, and not a samba one per se. Regards, Olivier Parisy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Saturday 17 May 2008 07:44:36 am Olivier Parisy wrote: John H Terpstra a écrit : I am a little lost at to what the problem is here. WINS does not require winbindd to be running. On the Linux system it requires: 1) In your /etc/nsswitch.conf file: ... hosts: files wins [NOTFOUND=return] dns ... 2) Install the samba file libnss_wins.so.2 in the /lib directory (or on 64-bit systems in the /lib64 directory) 3) Run nmbd That's it! What is so difficult? What makes this so complicated? If you do not need DNS, then don't even run it (or else just run a caching DNS server). Winbind is orthogonal to wins. They serve entirely differing purposes. Ah, thank you! That is exactly what I expected. I am pleased to read that winbind and wins are different beasts, as I have no interest in the former. The point is that, under Debian, the /lib/libnss_wins.so.2 file is distributed only in the winbind package, as confirmed by this search: http://packages.debian.org/search?searchon=contentskeywords=libnss_winsmo de=filenamesuite=stablearch=any So it seems like this is a packaging issue, and not a samba one per se. No. Not a packaging issue. winbind and wins NSS files are built out of the same code tree. It is a good idea to keep them together - just use what you need and ignore the rest. - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
John H Terpstra a écrit : No. Not a packaging issue. winbind and wins NSS files are built out of the same code tree. It is a good idea to keep them together - just use what you need and ignore the rest. That's a good point! Following this advice, I installed the winbind package but disabled winbind daemon's launch at start up (by deleting the proper /etc/rc2.d link). Things now work properly: I can ping NetBIOS names from my Linux machine, and my SMB share still work without modifications since winbind daemon is not launched. Thanks! Regards, Olivier. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Saturday 17 May 2008, Olivier Parisy wrote: It's good to avoid security=share, especially if you want to run WINS. I understand this. But that is simpler, and enough for me. That share is only used by local, trusted computers. Much less difficult than anything else involved here; it's just plain old good practice, will save you a headache or two down the road. And if you want non-static netbios resolution you need WINS. By the way, people on #samba seemed surprised by the fact that I needed to install the winbind packet to gain access to ls /lib/lib_wins.so.2. Is this the same with other distributions (I am using Debian Etch)?. Is there as an example a way I could compile and install only this library, without winbind? I mentioned this in a post last year sometime. Thought it was odd as well but no replies were forthcoming. If you compile samba w/o winbind you don't get the needed library. You don't have run winbind, but you need to compile samba that way. I should have definitely stated this from the start. My setting is the following: a Windows host embedding a Debian virtual machine. Both get Internet connectivity and IP addresses through the DHCP server of a small xDSL routing box. So yes, I could hardcode everything or, at the opposite of the scale, install a full DNS and WINS solution. Frankly I would just hardcode the hosts and lmhosts files (they should be identical) on both OS's. Way too fast and easy for that setup. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Thu, May 15, 2008 at 7:05 PM, Olivier Parisy [EMAIL PROTECTED] wrote: Hi all, I set up a Samba server (version 3.0.24) names Lamp on a Debian Etch distribution. It provides a guest (guest ok = yes, guest only = yes, security = SHARE) access to a share directory, which works fine. Indeed, I can access \\lamp\share from a Windows machine (named Ginger) without issuing a password. I can also ping the Linux machine from the Windows one using ping Lamp, and get the Windows machine IP from its NetBIOS name: # nmblookup Ginger querying Ginger on 192.168.1.255 192.168.1.22 Ginger00 But I cannot ping (or, more generally, resolve the name of) the Windows machine from the Linux one: # ping Ginger ping: unknown host Ginger I hence followed the guidelines from those links: http://ubuntuforums.org/archive/index.php/t-182824.html http://www.linuxquestions.org/questions/linux-networking-3/linuxsamba-pdc-cant-resolve-windows-names-622797/ Which means I installed winbind and modified /etc/nsswitch.conf by adding wins to the hosts entry. As I understand it, winbind provides a bridge between nmbd and gethostbyname() by using the Name Service Switch. Please note that I am not interested in the active directory part of winbind, nor in joining a domain, etc. Anyway, after I performed those modifications, ping Ginger actually worked. But then, \\lamp\share could not be accessed anymore (the error message was The specified group does not exist). Now, as soon as I remove the winbind package, I can access \\lamp\share again, but ping Ginger does not work anymore. I've been suggested on #samba to drop winbind and simply add wins support = yes to smb.conf; but then ping Ginger does not work any better. So, can I keep my simple share configuration, *and* integrate NetBIOS name resolution to my Linux system using Name Service Switch? FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 http://pastebin.ca/1019614 and nsswitch.conf here: http://pastebin.ca/1019612 http://pastebin.ca/1019612. Any hint would be greatly approciated. Wht should I look for? You just need to do this: http://lucasmanual.com/mywiki/SambaDomainController#head-8ae23b786749b4d46ef0e9ed22148e63eeab95e7 Lucas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBIOS name resolution from Linux
Hi, you can resolve this by following this howto. http://www.debian-administration.org/articles/343 Configuring Dynamic DNS DHCP set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Olivier Parisy Verzonden: vrijdag 16 mei 2008 2:05 Aan: samba@lists.samba.org Onderwerp: [Samba] NetBIOS name resolution from Linux Hi all, I set up a Samba server (version 3.0.24) names Lamp on a Debian Etch distribution. It provides a guest (guest ok = yes, guest only = yes, security = SHARE) access to a share directory, which works fine. Indeed, I can access \\lamp\share from a Windows machine (named Ginger) without issuing a password. I can also ping the Linux machine from the Windows one using ping Lamp, and get the Windows machine IP from its NetBIOS name: # nmblookup Ginger querying Ginger on 192.168.1.255 192.168.1.22 Ginger00 But I cannot ping (or, more generally, resolve the name of) the Windows machine from the Linux one: # ping Ginger ping: unknown host Ginger I hence followed the guidelines from those links: http://ubuntuforums.org/archive/index.php/t-182824.html http://www.linuxquestions.org/questions/linux-networking-3/linu xsamba-pdc-cant-resolve-windows-names-622797/ Which means I installed winbind and modified /etc/nsswitch.conf by adding wins to the hosts entry. As I understand it, winbind provides a bridge between nmbd and gethostbyname() by using the Name Service Switch. Please note that I am not interested in the active directory part of winbind, nor in joining a domain, etc. Anyway, after I performed those modifications, ping Ginger actually worked. But then, \\lamp\share could not be accessed anymore (the error message was The specified group does not exist). Now, as soon as I remove the winbind package, I can access \\lamp\share again, but ping Ginger does not work anymore. I've been suggested on #samba to drop winbind and simply add wins support = yes to smb.conf; but then ping Ginger does not work any better. So, can I keep my simple share configuration, *and* integrate NetBIOS name resolution to my Linux system using Name Service Switch? FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 http://pastebin.ca/1019614 and nsswitch.conf here: http://pastebin.ca/1019612 http://pastebin.ca/1019612. Any hint would be greatly approciated. Wht should I look for? Regards. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On 5/16/2008, L.P.H. van Belle ([EMAIL PROTECTED]) wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBIOS name resolution from Linux
First why use open dns servers. the dns servers of your provider is much less hops away. if you run you own dns server with caching modus on you have a very fast dns response and less traffic. in this example i first point to you own dns server. ( i also have forwarding dns servers in my bind9 config ) and i added 3 dns server of my provider in my resolve.conf show what i now get is. 1 search order makes sure my own dns is search first. 2 my own dns server responds, if not its forwarded to my providers dns with caching modes active. 3 every old request is very very fast because of the caching. 4 if my dns server fails, the linux server still has dns resolving provided by resolve.conf 's dns server. and, my local hosts in my lan are always correct even PTR records. i use this setup in my company. and it goes further. here i have 1 master dns + dhcp3 ( dynamic dns server + dhcp server ) every other server is dns slave. ( i have about 8 servers here ) and also across a wan. ( over vpn ) what i acomplised is a very stable and very fast, low cpu consuming dns setup. every server is capable of resolving any host/object in my lan/wan. so yes sure opendns is useable but if you really want it ... ow and i didnt say any randon ISP DNS. use your own IPS dns server ;-) Louis -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Charles Marcus Verzonden: vrijdag 16 mei 2008 15:30 Aan: samba@lists.samba.org Onderwerp: Re: [Samba] NetBIOS name resolution from Linux On 5/16/2008, L.P.H. van Belle ([EMAIL PROTECTED]) wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On 5/16/2008 10:08 AM, L.P.H. van Belle wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... First why use open dns servers. the dns servers of your provider is much less hops away. Hops really don't matter... most ISP DNS servers are unreliable... some are extremely unreliable... I said 'random' meaning, it really wouldn't matter what ISP you were using, I'd say the same thing... if you run you own dns server with caching modus on you have a very fast dns response and less traffic. Of course... but we weren't talking about someone using their own full DNS server, we were talking about using ISP DNS servers as forwarders... in this example i first point to you own dns server. ( i also have forwarding dns servers in my bind9 config ) and i added 3 dns server of my provider in my resolve.conf If you are running your own full blown DNS server, why on earth would you use *any* forwarders? Just use the root servers. But *if* you are going to use forwarders, then the opendns servers are much more reliable - and from my experience, much *faster* too - than any random ISP DNS servers someone might be using... I agree one should, at a minimum, run a caching DNS server locally - but again, use the opendns servers as your forwarders... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Friday 16 May 2008 09:22:43 am Charles Marcus wrote: On 5/16/2008 10:08 AM, L.P.H. van Belle wrote: set your resolve.conf to resolve on localhost first and set the search order. example of the resolve.conf search yourlocaldomain.internal.local otherdomain.com nameserver 127.0.0.1 nameserver ipofprovider Much better to use the opendns servers than any randon ISP DNS... First why use open dns servers. the dns servers of your provider is much less hops away. Hops really don't matter... most ISP DNS servers are unreliable... some are extremely unreliable... I said 'random' meaning, it really wouldn't matter what ISP you were using, I'd say the same thing... OK - now that we have split the atom regarding what might be the best DNS solution, how does this help resolve NetBIOS names within Linux? Have I missed something vital in this thread? Seems I must have. I'd like to know how you propose to store the name_type info in DNS? For example, how would you store MYSERVERNAME20 in DNS? Next, how will you teach the Windows client to search DNS for that info. After all, we are dealing with the NetBIOS name space. - John T. if you run you own dns server with caching modus on you have a very fast dns response and less traffic. Of course... but we weren't talking about someone using their own full DNS server, we were talking about using ISP DNS servers as forwarders... in this example i first point to you own dns server. ( i also have forwarding dns servers in my bind9 config ) and i added 3 dns server of my provider in my resolve.conf If you are running your own full blown DNS server, why on earth would you use *any* forwarders? Just use the root servers. But *if* you are going to use forwarders, then the opendns servers are much more reliable - and from my experience, much *faster* too - than any random ISP DNS servers someone might be using... I agree one should, at a minimum, run a caching DNS server locally - but again, use the opendns servers as your forwarders... -- Best regards, Charles -- John H Terpstra Samba-Team Member Phone: +1 (512) 970-0256 Author: The Official Samba-3 HOWTO Reference Guide, 2 Ed., ISBN: 0131882228 Samba-3 by Example, 2 Ed., ISBN: 0131882221X Hardening Linux, ISBN: 0072254971 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBios name resolution from WINDOWS
Hi, I've been following a similar and current thread about name resolution from LINUX side. I have exactly the opposite problem (running ubuntu 7.10 on a network with a mixture ubuntu 6.06, WinXP and WinVista boxes) The winboxes cannot see or mount this 7.10 box I can mount WinPC shares on this 7.10 box. I was wondering about firewalls, but I can ping this 7.10 from the WinBox by IP address but _not_ by netbios name. I do not have any issues on the 8 other ubuntu 6.06 boxes on the network. The smb.conf files are largely the same on both the 6.06 boxes and the 7.10 box. If I ping by IP - I get a response. If I ping gm0: Ping request could not find gm0. If I ping gm0.geograph.co.za then it works and I get the correct IP address too. The above pings are from a VISTA box. ps -ef shows nmbd is running By the way, from windows vista explorer, _all_ of these attempts return : windows cannot find \\x. check spelling and try again. \\gm0 \\gm0.geograph.co.za \\192.168.0.1# which is the fixed IP for gm0, yet explorer cannot see it this way Yet \\gl0 and all the other linux boxes are accessible from this Vista box. BTW: I'm not considering firewall Squid proxy stuff on this gm0 box because ping does work with full name (gm0.geograph.co.za) Can someone please give me some ideas to work on? Thanks, Zoltan -- === Zoltan Szecsei Geograph (Pty) Ltd. P.O. Box 31255, Tokai 7966, South Africa. B3-106 Tokai Village, cnr Vans/Tokai Rds, Tokai 7945, Western Cape, South Africa. Tel: +27-21-7154329 Mobile: +27-83-6004028 Fax: +27-86-6115323 === -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
A few thoughts, take from them what you will (and remember, free advice is worth what you pay for it). It's really good to have proper IP name resolution. Requires DNS or (ugh) hosts files. It can also be good to have NetBIOS name resolution, if you have the need (Windows type browsing and sharing in non-native AD environments). Implies WINS or (ugh) lmhosts files for resolution (or you're left only with broadcasts). It's good to avoid security=share, especially if you want to run WINS. And yes, a proper setup using security=user can provide guest shares. Winbind is normally used to authenticate against Windows servers that are running WINS or AD, so that you don't need to duplicate the Windows user/groups. You don't mention how big your network is, but if you're dealing with 5 or more systems I highly suggest both DNS and WINS over their static equivalents, hosts and lmhosts, respectively. Even with fewer systems, it can be a good idea to bother with the setup if you intend to grow or want flexibility. If you run a WINS server, you need to tell your clients to register with it (this is easily done with DHCP - then you don't have to manually configure them), or it wont contain their information. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On 5/16/2008, John H Terpstra ([EMAIL PROTECTED]) wrote: OK - now that we have split the atom regarding what might be the best DNS solution, how does this help resolve NetBIOS names within Linux? Have I missed something vital in this thread? Seems I must have. I was just responding to the recommendation to use ISP DNS servers for forwarders... sorry for the OT noise... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBios name resolution from WINDOWS
On Friday 16 May 2008 09:09:53 am Zoltan Szecsei wrote: Hi, I've been following a similar and current thread about name resolution from LINUX side. I have exactly the opposite problem (running ubuntu 7.10 on a network with a mixture ubuntu 6.06, WinXP and WinVista boxes) The winboxes cannot see or mount this 7.10 box I can mount WinPC shares on this 7.10 box. I was wondering about firewalls, but I can ping this 7.10 from the WinBox by IP address but _not_ by netbios name. I do not have any issues on the 8 other ubuntu 6.06 boxes on the network. The smb.conf files are largely the same on both the 6.06 boxes and the 7.10 box. If I ping by IP - I get a response. If I ping gm0: Ping request could not find gm0. If I ping gm0.geograph.co.za then it works and I get the correct IP address too. The above pings are from a VISTA box. ps -ef shows nmbd is running By the way, from windows vista explorer, _all_ of these attempts return : windows cannot find \\x. check spelling and try again. \\gm0 \\gm0.geograph.co.za \\192.168.0.1# which is the fixed IP for gm0, yet explorer cannot see it this way Yet \\gl0 and all the other linux boxes are accessible from this Vista box. BTW: I'm not considering firewall Squid proxy stuff on this gm0 box because ping does work with full name (gm0.geograph.co.za) Can someone please give me some ideas to work on? Thanks, Zoltan Zoltan, Check on your Windows client, in the TCP/IP Advanced settings that you have enabled NetBIOS over TCP/IP. - John T. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Friday 16 May 2008, L.P.H. van Belle wrote: so yes sure opendns is useable but if you really want it ... Actually it's horrible for mail servers. Although fine if you value its ability to block sites for desktop use. At sites that I use it, I've needed 2 DNS caches, one that forwards to OpenDNS for non-local systems that desktops connects to, and one that resolves via the root servers for the mail server. For my own use I prefer to resolve via the root servers. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On 5/16/2008 1:45 PM, Chris Smith wrote: so yes sure opendns is useable but if you really want it ... Actually it's horrible for mail servers. Actually, no, its not - it works fine - and has been working fine for well over a year - for some of mine... This is OT though, and probably should be taken off list... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS name resolution from Linux
On Friday 16 May 2008, Charles Marcus wrote: On 5/16/2008 1:45 PM, Chris Smith wrote: so yes sure opendns is useable but if you really want it ... Actually it's horrible for mail servers. Actually, no, its not - it works fine - and has been working fine for well over a year - for some of mine... Totally disagree. This is OT though, and probably should be taken off list... I agree, but no need to discuss it any longer. The readers can come to their own conclusions. -- Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS name resolution from Linux
Hi all, I set up a Samba server (version 3.0.24) names Lamp on a Debian Etch distribution. It provides a guest (guest ok = yes, guest only = yes, security = SHARE) access to a share directory, which works fine. Indeed, I can access \\lamp\share from a Windows machine (named Ginger) without issuing a password. I can also ping the Linux machine from the Windows one using ping Lamp, and get the Windows machine IP from its NetBIOS name: # nmblookup Ginger querying Ginger on 192.168.1.255 192.168.1.22 Ginger00 But I cannot ping (or, more generally, resolve the name of) the Windows machine from the Linux one: # ping Ginger ping: unknown host Ginger I hence followed the guidelines from those links: http://ubuntuforums.org/archive/index.php/t-182824.html http://www.linuxquestions.org/questions/linux-networking-3/linuxsamba-pdc-cant-resolve-windows-names-622797/ Which means I installed winbind and modified /etc/nsswitch.conf by adding wins to the hosts entry. As I understand it, winbind provides a bridge between nmbd and gethostbyname() by using the Name Service Switch. Please note that I am not interested in the active directory part of winbind, nor in joining a domain, etc. Anyway, after I performed those modifications, ping Ginger actually worked. But then, \\lamp\share could not be accessed anymore (the error message was The specified group does not exist). Now, as soon as I remove the winbind package, I can access \\lamp\share again, but ping Ginger does not work anymore. I've been suggested on #samba to drop winbind and simply add wins support = yes to smb.conf; but then ping Ginger does not work any better. So, can I keep my simple share configuration, *and* integrate NetBIOS name resolution to my Linux system using Name Service Switch? FWIW, I posted my smb.conf here: http://pastebin.ca/1019614 http://pastebin.ca/1019614 and nsswitch.conf here: http://pastebin.ca/1019612 http://pastebin.ca/1019612. Any hint would be greatly approciated. Wht should I look for? Regards. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios name resolution inside linux via samba?
Hello, I have setup up samba on my pc and everything is working great. I setup my writable shared folders I can view other servers/pcs on the network using gnome but sometimes I need to debug some networking issues and I would like to for example: ping myserver4 ping: unknown host myserver4 Is there a way to setup up linux to use samba for name resolution? The only way I know right now is to add myserver4 to /etc/hosts, but since there is 70 computer on a network is there an easier way? Automatically add all of them to /etc/hosts? or setup linux to use samba name resolution tools ? or? OS: Debian Stable setup: http://lucasmanual.com/mywiki/SambaDomainController Thanks. Lucas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios sid and domain sid
Hi all, I'm installing a pdc samba+openldap on a debian etch server. I have this problem: with ldap configuration ended successfully, I start samba for the first time, so samba adds a sambaDomainName entry in ldap database. the problem is that this entry has a wrong sid (different from the one returned by net getlocalsid). Then I have errors in granting privileges and so on. In particular I have 2 different sids for domain (the one wrong) and or netbios name (the one right). Why? is it a samba bug? I use samba 3.0.24-6etch9. Thanks in advance, Fabio -- Dott. Fabio Marcone 2T srl Telefono+39 - 0871- 540154 Fax +39 - 0871- 571594 Email fabio.marcone(AT)duet.it Indirizzo Viale B. Croce 573 66013 Chieti Scalo (CH) GNU/Linux registered user #400424 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NETBIOS browse by name
I'm currently using samba3.0.24 ( and have tried 25): If I use a windows box to browse to my share by name it does not work. If I browse by ip it works fine. If I use samba2 the browse works fine. The netbios name I provide in the smb.conf is longer than the 15 char max. However in samba2 it used to truncate this. In Samba3 it appears to try to truncate, however it takes the first 16 characters and then it appears to append the server string to the end of the netbios name. You can see this under windows xp. To resolve my problem I had to truncate the netbios name in the smb.conf file to 15 chars. Anything above this will prvent you from browsing by name from windows. Seems like a bug to me. Samba2 handled this just fine. To duplicate just set your server string and netbios name. Make the netbios name longer than 15 characters. I used the following in my smb.conf to cause the problem. [global] workgroup = COMPANY4 server string = house-controller-5000-0019D1DF9BWW netbios name = 0019D1DF9BWW-house-controller-5000 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [NetBIOS] Registering new name?
Hi Gilles, At 05:29 21-08-2007, Gilles Ganault wrote: I'm trying to register a new name on a server so that clients can locate it by broadcasting its NetBIOS name. At this point, this little VB code does register the name successfully, but it's not listed in net name and net send to it fails: == Private Sub Command1_Click() Dim ncbInfo As NCB Dim sMachine As String * NCBNAMSZ Dim bRet As Byte '===1. Send RESET With ncbInfo .ncb_command = NCBRESET End With bRet = Netbios(ncbInfo) MsgBox ncbInfo.ncb_retcode, , ncbInfo.ncb_num '===2. Register name sMachine = SERVER_NAME Chr(3) With ncbInfo .ncb_command = NCBADDNAME .ncb_name = sMachine '.ncb_lana_num = H0 End With .ncb_name is a Byte array. bRet = Netbios(ncbInfo) MsgBox ncbInfo.ncb_retcode, , ncbInfo.ncb_num You are assuming that the NetBios call will return the correct value of .ncb_retcode after that call has been complicated. The code may not have registered the NetBIOS name successfully. You should verify the value of .ncb_cmd_cplt and only lookup the .ncb_retcode value after the NetBios command has been completed. Regards, -sm -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] [NetBIOS] Registering new name?
Hello I'm having a hard time finding information about NetBIOS. Maybe someone here has good experience with this API, so I figured I could try asking here, although the question is specifically on how to use NetBIOS in an all-Windows LAN from Visual Basic :-/ I'm trying to register a new name on a server so that clients can locate it by broadcasting its NetBIOS name. At this point, this little VB code does register the name successfully, but it's not listed in net name and net send to it fails: == Private Sub Command1_Click() Dim ncbInfo As NCB Dim sMachine As String * NCBNAMSZ Dim bRet As Byte '===1. Send RESET With ncbInfo .ncb_command = NCBRESET End With bRet = Netbios(ncbInfo) MsgBox ncbInfo.ncb_retcode, , ncbInfo.ncb_num '===2. Register name sMachine = SERVER_NAME Chr(3) With ncbInfo .ncb_command = NCBADDNAME .ncb_name = sMachine '.ncb_lana_num = H0 End With bRet = Netbios(ncbInfo) MsgBox ncbInfo.ncb_retcode, , ncbInfo.ncb_num 'Can't use net send 'C:\nbtstat -n ' 'FRED 03 UNIQUE Registered 'MY_GREAT_SERVER03 UNIQUE Registered ' 'C:\net name 'Name '- 'MYPUTER 'FRED 'The command completed successfully. ' 'C:\net send fred test 'The message was successfully sent to FRED. ' 'C:\net send my_great_server test 'An error occurred while sending a message to MY_GREAT_SERVER. ' 'The message alias could not be found on the network. 'C:\ping my_great_server 'Ping request could not find host my_great_server. Please check the name and try 'again. ' 'C:\ping fred 'Ping request could not find host fred. Please check the name and try again. '===3. Have client hosts send broadcast to locate '===4. Clients connect to \\MY_GREAT_SERVER\pipes\mypipe to tx/rx data End Sub == Any idea why it's not working? Thank you. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NETBIOS (NetBT) Issues
Using Ubuntu 6.06.1, Samba 3.0.22, VMWare. Cannot access shares using netbios name, but ip address works. From a workstation command prompt (member of same domain as samba), used net view netbiosname and got system error 5, used net view ipaddress and got list of shares. Ran ethereal and attempted a session with the server using netbios name. NBSS and SMB packets are being exchanged with the correct server so apparently it can resolve netbiosname to ipaddress. Finally, i see a SMB packet with a STATUS_LOGON_FAILURE (0xc06d) comming back from the ip of the netbiosname server. Why is the login failing when I use netbiosname but not ipaddress when netbiosname is apparently resolved to the proper ip. Need help tracking this down, thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows != Samba - NETBIOS name handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Masson wrote: [EMAIL PROTECTED] etc]# net ads join -U Administrator Administrator's password: [2006/11/01 13:14:34, 0] libads/ldap.c:ads_join_realm(1763) ads_join_realm: ads_add_machine_acct failed (uk1-sysstg-sqlsyslogtest): Internal (implementation specific) error ads_join_realm: Internal (implementation specific) error Looking at packet trace output suggests it's because of NETBIOS name length limitations. IIRC, checks were introduced to inform you of names 15 characters. Please test a join using the net command from 3.0.23c cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFWJd0IR7qMdg1EfYRAgwcAJ46KkdHyJQ/i3f2BzAQOu39ULnaugCgg0rj tH/PKUwKd1NCU5/Q3SOrhM8= =xV4D -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios Problem
Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomain localhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Problem
Jeff, Sounds like a name resolution problem on your XP workstation. Make sure the following line is in C:\WINDOWS\System32\Drivers\etc\hosts on you XP workstation: 192.168.1.1 www Then try to ping the www from your workstation again. If it pings, then \\www sould also work. Sander On Sun, 2006-11-12 at 07:10 -0600, Jeff Herbeck wrote: Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomain localhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Problem
Thanks! That worked, but that just seems like a way to trick it into working. I have a unbuntu workstation that can't see www and another XP machine that can't see www. Even with the change to my hosts file on this XP box, I still can't go into network neighborhood and see www. Every other time I have setup samba it was browseable and worked from any other computer with no configuration Jeff On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Jeff, Sounds like a name resolution problem on your XP workstation. Make sure the following line is in C:\WINDOWS\System32\Drivers\etc\hosts on you XP workstation: 192.168.1.1 www Then try to ping the www from your workstation again. If it pings, then \\www sould also work. Sander On Sun, 2006-11-12 at 07:10 -0600, Jeff Herbeck wrote: Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomainlocalhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Problem
Are your workstations and your server on the same subnet? Is your nmbd service running? On Sun, 2006-11-12 at 08:42 -0600, Jeff Herbeck wrote: Thanks! That worked, but that just seems like a way to trick it into working. I have a unbuntu workstation that can't see www and another XP machine that can't see www. Even with the change to my hosts file on this XP box, I still can't go into network neighborhood and see www. Every other time I have setup samba it was browseable and worked from any other computer with no configuration Jeff On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Jeff, Sounds like a name resolution problem on your XP workstation. Make sure the following line is in C:\WINDOWS\System32\Drivers\etc\hosts on you XP workstation: 192.168.1.1 www Then try to ping the www from your workstation again. If it pings, then \\www sould also work. Sander On Sun, 2006-11-12 at 07:10 -0600, Jeff Herbeck wrote: Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomain localhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Problem
does your xp machine have the same workgroup as the samba server netbois? if not you might want to change the XP workgroup name to the samba server Netbois name, restart XP and try to re-browse the network again. On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Are your workstations and your server on the same subnet? Is your nmbd service running? On Sun, 2006-11-12 at 08:42 -0600, Jeff Herbeck wrote: Thanks! That worked, but that just seems like a way to trick it into working. I have a unbuntu workstation that can't see www and another XP machine that can't see www. Even with the change to my hosts file on this XP box, I still can't go into network neighborhood and see www. Every other time I have setup samba it was browseable and worked from any other computer with no configuration Jeff On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Jeff, Sounds like a name resolution problem on your XP workstation. Make sure the following line is in C:\WINDOWS\System32\Drivers\etc\hosts on you XP workstation: 192.168.1.1 www Then try to ping the www from your workstation again. If it pings, then \\www sould also work. Sander On Sun, 2006-11-12 at 07:10 -0600, Jeff Herbeck wrote: Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomain localhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Problem
Yes, everything is on the same subnet. I run a simple 192.168.1.x 255.255.2550 My workgroup is workgroup on windows and in my smb.conf. On 11/12/06, M Azer [EMAIL PROTECTED] wrote: does your xp machine have the same workgroup as the samba server netbois? if not you might want to change the XP workgroup name to the samba server Netbois name, restart XP and try to re-browse the network again. On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Are your workstations and your server on the same subnet? Is your nmbd service running? On Sun, 2006-11-12 at 08:42 -0600, Jeff Herbeck wrote: Thanks! That worked, but that just seems like a way to trick it into working. I have a unbuntu workstation that can't see www and another XP machine that can't see www. Even with the change to my hosts file on this XP box, I still can't go into network neighborhood and see www. Every other time I have setup samba it was browseable and worked from any other computer with no configuration Jeff On 11/12/06, S. J. van Harmelen [EMAIL PROTECTED] wrote: Jeff, Sounds like a name resolution problem on your XP workstation. Make sure the following line is in C:\WINDOWS\System32\Drivers\etc\hosts on you XP workstation: 192.168.1.1 www Then try to ping the www from your workstation again. If it pings, then \\www sould also work. Sander On Sun, 2006-11-12 at 07:10 -0600, Jeff Herbeck wrote: Hello Everyone, I have recently built a new CentOS 4 server and I am having trouble with Samba and specifically Netbios names. The server also acts as a router, firewall, dhcp, and so on. I have a very simple setup and no matter what I try, I can't get to my samba server by name. The servers IP is: 192.168.1.1 The server name is: www I can not ping www (my XP workstation says could not find host www) I can not access my samba shares with \\www If I type in \\192.168.1.1 everything works fine I kept thinking it was my firewall (shorewall configured with webmin), but even when I turn the firewall off, I still have the same problem. I have tried many combinations of opened ports on my firewall with no success. Right now I have: loc to firewall open on UDP 137 loc to firewall open on TCP 137, 138, 139 loc to firewall open on TCP 445 I had a fedora server in the past and samba worked like a dream. I'm down to a really simple smb.conf. Here that is: [global] workgroup = workgroup # netbios name = WWW(I have tried it with and without this line) security = user encrypt passwords = yes [homes] browseable = yes writeable = yes Here is my hosts file 127.0.0.1 www.mydomain.com www localhost.localdomain localhost 192.168.1.1 www Does anyone have any ideas? Thanks in advance, Jeff -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios and Zeroconf?
Hi, a totally simple, but maybe totally useless question: is there some (small) possibility to theoretically turn off the dns and service resolution provided by samba/netbios and use zeroconf/dns-sd instead? I know it won't be much help for windows users, because they won't find the shares anymore, but maybe there'll be a zeroconf implementation on windows someday? greetings fabian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios and Zeroconf?
Fabian Zeindl wrote: Hi, a totally simple, but maybe totally useless question: is there some (small) possibility to theoretically turn off the dns and service resolution provided by samba/netbios and use zeroconf/dns-sd instead? To make Samba use zeroconf/dns-sd for name resolution set in smb.conf:[1] name resolve order = host And use something like this in your nsswitch.conf file:[2] hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 To prevent other machines from finding you via netbios add the following to smb.conf:[3] disable netbios = yes Other machines can still find you via DNS unless you don't send a hostname to the DHCP server (and it doesn't assign you one). I'm not quite sure why you'd want to mess with DNS though because it could effect so many other services. I know it won't be much help for windows users, because they won't find the shares anymore, but maybe there'll be a zeroconf implementation on windows someday? Never tried it, but these links look relevant: http://www.stg.com/zeroconf_explorer.html http://www.apple.com/support/downloads/bonjourforwindows.html Good luck! Michael Schurter [1] http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html#NAMERESOLVEORDER [2] http://0pointer.de/lennart/projects/nss-mdns/ [3] http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html#DISABLENETBIOS -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios name resolution stops working after device change
Hi there. This is with regards to samba-3.0.23c, on FreeBSD 6.0-RELEASE-p12 Previously I had Samba up and running without any problems. Then I decided to do a tiny upgrade by simply switching to a new motherboard, while keeping all other hardware and software aspects the same. However, after the upgrade, netbios name resolution seems to have stopped working somehow. \\servername lookups no longer work from other workgroup clients. \\serverip works fine though. The configuration was not changed at all during the migration. The only changes were some of the mount entries and the network device change from rl0 to sk0, with corresponding changes in /etc/rc.conf. After that I tried using another card on xl0, but with the same results. My Samba config is such that the network only relies on broadcast to learn the names of other workstations. No WINS server, or listing hostnames in /etc/hosts or lmhosts. Here's an nmbd logfile snippet. The Samba server here is MARIO, and workgroup WORKGROUP: [snip start] [2006/11/07 22:11:50, 0] nmbd/nmbd.c:main(699) Netbios nameserver version 3.0.23c started. Copyright Andrew Tridgell and the Samba Team 1992-2006 [2006/11/07 22:11:50, 2] nmbd/nmbd.c:main(723) Becoming a daemon. [2006/11/07 22:11:50, 2] lib/tallocmsg.c:register_msg_pool_usage(61) Registered MSG_REQ_POOL_USAGE [2006/11/07 22:11:50, 2] lib/dmallocmsg.c:register_dmalloc_msgs(71) Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED [2006/11/07 22:11:50, 2] lib/interface.c:add_interface(81) added interface ip=10.11.12.3 bcast=10.11.12.255 nmask=255.255.255.0 [2006/11/07 22:11:50, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:10.11.12.3 Broadcast address:10.11.12.255 Subnet mask:255.255.255.0 [2006/11/07 22:11:50, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2006/11/07 22:11:50, 2] nmbd/nmbd_subnetdb.c:make_subnet(144) making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet mask:0.0.0.0 [2006/11/07 22:11:50, 2] nmbd/nmbd_lmhosts.c:load_lmhosts_file(41) load_lmhosts_file: Can't open lmhosts file /usr/local/etc/lmhosts. Error was No such file or directory [2006/11/07 22:12:06, 2] nmbd/nmbd_elections.c:send_election_dgram(41) send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:08, 2] nmbd/nmbd_elections.c:send_election_dgram(41) send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:10, 2] nmbd/nmbd_elections.c:send_election_dgram(41) send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:12, 2] nmbd/nmbd_elections.c:send_election_dgram(41) send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:14, 2] nmbd/nmbd_elections.c:send_election_dgram(41) send_election_dgram: Sending election packet for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:14, 2] nmbd/nmbd_elections.c:run_elections(204) run_elections: Won election for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:14, 2] nmbd/nmbd_become_lmb.c:become_local_master_browser(537) become_local_master_browser: Starting to become a master browser for workgroup WORKGROUP on subnet 10.11.12.3 [2006/11/07 22:12:24, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) * Samba name server MARIO is now a local master browser for workgroup WORKGROUP on subnet 10.11.12.3 * [snip end] There doesn't seem to be any response from the other workstations during the election. In fact, another workstation, PHOENIX, has already assumed the role of local master browser, but didn't relieve it's role when MARIO appears: [snip start] C:\nbtstat -a phoenix Wireless Network Connection 4: Node IpAddress: [10.11.12.2] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status - PHOENIX00 UNIQUE Registered PHOENIX20 UNIQUE Registered WORKGROUP 00 GROUP Registered WORKGROUP 1E GROUP Registered WORKGROUP 1D UNIQUE Registered ..__MSBROWSE__.01 GROUP Registered MAC Address = 00-16-B6-56-8E-40 [snip end] Some other command responses that may be helpful:- [from MARIO start] nmblookup mario added interface ip=10.11.12.3 bcast=10.11.12.255 nmask=255.255.255.0 querying mario on 10.11.12.255 name_query failed to find name mario nmblookup workgroup added interface ip=10.11.12.3 bcast=10.11.12.255 nmask=255.255.255.0 querying workgroup on 10.11.12.255 Got a positive name query response from 10.11.12.2 ( 10.11.12.2 ) 10.11.12.2 workgroup00 nmblookup -m workgroup added interface ip=10.11.12.3 bcast=10.11.12.255 nmask=255.255.255.0 querying workgroup on 10.11.12.255 Got a positive name query response from
[Samba] Windows != Samba - NETBIOS name handling
Hi, I'm using samba just for its net join functionality. Computer accounts and kerberos keytabs are created by Samba in Active Directory via net ads join, then used by UNIX clients to authorise and authenticate via LDAP and Kerberos. Samba works perfectly until the computers hostname is longer than 15 characters. Then any attempt to join the domain fails with: [EMAIL PROTECTED] etc]# net ads join -U Administrator Administrator's password: [2006/11/01 13:14:34, 0] libads/ldap.c:ads_join_realm(1763) ads_join_realm: ads_add_machine_acct failed (uk1-sysstg-sqlsyslogtest): Internal (implementation specific) error ads_join_realm: Internal (implementation specific) error Looking at packet trace output suggests it's because of NETBIOS name length limitations. So I specify a legal NETBIOS name in smb.conf, and the join succeeds. The problem is now that this computer is _completely_ identified to AD by this NETBIOS name. Both the kerberos tickets and the DNS name for this computer are linked to the NETBIOS name, even though this is different from the UNIX hostname. If this were a Microsoft AD limitation, I could write this off, but it seems this is a Samba problem. From: http://technet2.microsoft.com/WindowsServer/en/library/8ec96981-6b1a-48ec-bd3e-d8d43bc814311033.mspx?mfr=true --- --- To ensure interoperability between NetBIOS and DNS naming in Windows, a new naming parameter called the NetBIOS computer name was introduced. The value of this parameter, which is not required in a Windows 2000 or Windows Server 2003 environment, is derived from the first 15 characters of the DNS full computer name. When the full computer name is a combination of the computer name and the primary DNS suffix for the computer, the impact of renaming and making the transition from a NetBIOS namespace to a DNS namespace can be minimal. Users continue to focus on the short computer name. If this name is 15 characters or less, it can be made identical to the NetBIOS computer name. The administrator can then also assign a DNS domain name for each computer. This can be done using remote administration tools. -- -- It seems Windows allows the NETBIOS name and computer DNS name to be separate, but Samba doesn't. A look inside the AD properties for a computer account shows these can be different, but a samba join forces them to be the same. I've also tried pre-creating the computer accounts in AD - this still happens. Is there any way round this issue? (And no rename 100+ production servers suggestions please ;-) ) thanks James Masson -- Redhat EL4 samba-client-3.0.10-1.4E.9 samba-common-3.0.10-1.4E.9 also tried with samba.org samba-3.0.22-1 --- smb.conf workgroup = TESTING ; netbios name = UK1-SYSSTG-SQLS realm = TESTING.LOCAL.INVALID security = ads use kerberos keytab = True --- Windows 2003 R2 ** Confidentiality : This e-mail and any attachments are intended for the addressee only and may be confidential. If they come to you in error you must take no action based on them, nor must you copy or show them to anyone. Please advise the sender by replying to this e-mail immediately and then delete the original from your computer. Opinion : Any opinions expressed in this e-mail are entirely those of the author and unless specifically stated to the contrary, are not necessarily those of the authors employer. Security Warning : Internet e-mail is not necessarily a secure communications medium and can be subject to data corruption. We advise that you consider this fact when e-mailing us. Viruses : We have taken steps to ensure that this e-mail and any attachments are free from known viruses but in keeping with good computing practice, you should ensure that they are virus free. ___ This message has been checked for all known viruses by UUNET delivered through the MessageLabs Virus Control Centre. For further information visit http://www.uk.uu.net/products/security/virus/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios over more then one protocol
Hi, i'm reading: samba-3.0.20a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html#id2564441 ... The election process is /fought out, so to speak/ over every NetBIOS network interface. In the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both protocols, the election will be decided over both protocols. As often happens, if the Windows 9x/Me machine is the only one with both protocols, then the LMB may be won on the NetBIOS interface over the IPX protocol. Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail... what exactly happens if theres a netbios/ipx machine in one workgroup (only windows machines) that wins the election for the local master browser (theres one in every workgroup right?) The network neighborhood wouldn't show anything right? Would anything change if all machines install ipx? Second scenario: this workgroup is in a subnet with other workgroups (no ipx installed), every workgroup has its lmb. The other workgroups should show up in the network neighborhood except for the machines from the ipx workgroup? greets Julius -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios over more then one protocol
Why do you have IPX installed? Are you running an older Netware server in the same network? If it is not needed, maybe you can remove the IPX protocol from the Win9x machines? Michael julius Junghans told me on 10/27/2005 16:11: Hi, i'm reading: samba-3.0.20a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html#id2564441 ... The election process is /fought out, so to speak/ over every NetBIOS network interface. In the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both protocols, the election will be decided over both protocols. As often happens, if the Windows 9x/Me machine is the only one with both protocols, then the LMB may be won on the NetBIOS interface over the IPX protocol. Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail... what exactly happens if theres a netbios/ipx machine in one workgroup (only windows machines) that wins the election for the local master browser (theres one in every workgroup right?) The network neighborhood wouldn't show anything right? Would anything change if all machines install ipx? Second scenario: this workgroup is in a subnet with other workgroups (no ipx installed), every workgroup has its lmb. The other workgroups should show up in the network neighborhood except for the machines from the ipx workgroup? greets Julius -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios over more then one protocol
Michael Barnes wrote: Why do you have IPX installed? Are you running an older Netware server in the same network? If it is not needed, maybe you can remove the IPX protocol from the Win9x machines? Michael No, i don't use Win9x anymore. I'm just interested what might happen because i used 9x for some years. Julius -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS Name Resolution Problem?
All, 1. Here is my network configuration: One NT4 PDC One NT4 BDC Two Sun boxes, both configured as Domain Member servers running Samba version 3.0.10 providing file and print sharing. Three Windows 2000 boxes configured as Citrix servers Two Sun boxes configured as Sun Ray servers (used in conjunction with the Citrix servers) One UNIX box used as a DNS Master Server One UNIX box used as a DNS Slave Server One UNIX box used as an LDAP server Several Mac OS 9 workstations Several Mac OS X workstations Several Sun workstations Note: At the moment there is no synchronization between the PDC/BDC and the LDAP server. All syncronization (passwords, users, groups, etc are done manually). 2. Problem: My Windows 2000 clients can see and use all samba services provided by both servers. However, there appears to be NetBIOS resolution problems at the PDC and BDC. When running smbclient L samba server on both samba servers, shares are listed. However, in the work group portion of the report I get the following result: Session request to SAMBA_SERVER failed (Called name not present) Session request to *SMBSERVER failed (Called name not present) NetBIOS over TCP disabled workgroup unavailable. The only reason I noticed this problem is that Mac OS X clients under development could not connect to the samba shares. However, Samba, as is, is satisfying my user base with no problems. 3. Troubleshooting Both Samba servers passed ping tests. To themselves, to the PDC and BDC, and from the PDC and BDC to the Samba servers. No firewalls are in use. Ran testparm against the smb.conf file. Passed. Verified that the smbd and nmbd daemons were running on both Samba servers. Ran nmblookup B samba_server on both servers. Passed. Ran nmblookup B domain_controller * on both the PDC and BDC. Passed. From both Samba servers ran nmblookup d 2 *. Passed. On both Samba servers, ran the smbclient test listed in the above problem section with the noted results. From both the PDC and BDC, ran the net view command without any arguments. Both Samba servers were listed. From both the PDC and BDC ran net view \\samba _server and got the following error: System error 53 has occurred The network path was not found Finally, I ran the smbclient and nmblookup tests on both Samba servers with a debugging level of 4. The tests produced the following fatal error: Error loading module /usr/local/smaba/charset/ ..so. The modules each server was attempting to load were not in the /usr/local/samba/charset directory. 4. Questions Is this a hostname resolution problem? Are the missing charset modules causing my problem? Will a recompilation fix the problem, or will I have to do a complete de-installation? Is there a work-around? - This mail sent through IMP: http://horde.org/imp/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS needed?
Sorry if this sounds like I'm confused. I am. I am new to Samba and Solaris. I've got Samba 3.0.10 running on Solaris 9. The only windows box I can see or access the shares from is my Windows 2003 ADC which happens to be the only box running NetBIOS in the domain. I have started up a WINS server and added the servers IP to the samba.conf file. The samba server has registered in WINS but I still can not get to the Samba server via my XP client. If I turn NetBIOS on for the client it works. Is there a way to make this work without turning on NetBIOS? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios description
Guys I have a samba server that has joined and existing 2000 domain (used for squid NTLM auth) When using My network places on an xp server i see the following Samba 3.0.11 (Squid-server) Now the servers name is Squid-server, and the description seems to be Samba 3.0.11. How do i remove this description ? I have look through the smb.conf man pages and can find where you set the netbios name but not the descrition. Cheers Graeme -- Chaos. Panic. Disorder. My work here today is done -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE [Samba] netbios description
Hi, server string parameter in smb.conf --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 [EMAIL PROTECTED] a écrit sur 10/06/2005 11:35:50 : Guys I have a samba server that has joined and existing 2000 domain (used for squid NTLM auth) When using My network places on an xp server i see the following Samba 3.0.11 (Squid-server) Now the servers name is Squid-server, and the description seems to be Samba 3.0.11. How do i remove this description ? I have look through the smb.conf man pages and can find where you set the netbios name but not the descrition. Cheers Graeme -- Chaos. Panic. Disorder. My work here today is done -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios Alias
I am trying to setup a Netbois alias that uses it's own smb.conf file. I have made the following changes to the original smb.conf file: netbois alias = TPUB02 include = /usr/local/samba/lib/smb.conf.%L For some reason the smb.conf file in the include statement does not work. In touble shooting this issue I was able to hardcode the smb.conf file name in the include statement and that does work. include = /usr/local/samba/lib/smb.conf.tpub02 I would appreciate any help with fixing this problem. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Alias
Hello Ricky, Monday, May 23, 2005, 2:41:50 PM, you wrote: FR include = /usr/local/samba/lib/smb.conf.tpub02 FR I would appreciate any help with fixing this problem. Maybe if the netbios alias is uppercase, also the file should be smb.conf.TPUB02 instead of tpub02. have you tried uppercase? -- Fabio Kurgan Muzzi -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Alias
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Freeman, Ricky wrote: | I am trying to setup a Netbois alias that uses it's | own smb.conf file. I have made the following changes | to the original smb.conf file: | | netbois alias = TPUB02 | include = /usr/local/samba/lib/smb.conf.%L | | For some reason the smb.conf file in the include | statement does not work. In touble shooting this issue | I was able to hardcode the smb.conf file name | in the include statement and that does work. | | include = /usr/local/samba/lib/smb.conf.tpub02 | | I would appreciate any help with | fixing this problem. To use netbios aliases with Windows 2000 and later clients, you have to force the client to use port 139. So set 'smb ports = 139' in smb.conf. Alternatively you can use a multi-homed Samba box, assign a different DNS name to each [virtual] interface and use the %i var in place of %L. cheers, jerry = Alleviating the pain of Windows(tm) --- http://www.samba.org GnuPG Key- http://www.plainjoe.org/gpg_public.asc I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkdS6IR7qMdg1EfYRAv0tAKCsqbUddj/TIlKhatdh0qP70Z2iGACgxA4d kwa0iW1YCtuqk/1P/iJs71o= =PBCs -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios name resolution
Hello everyone, I wrote an email a couple of days ago, but haven't received an answer yet. Perhaps it was a bit confusing, so I'll try again. How can I make sure that NetBIOS name lookups work in the config file? I mean the %m macro. What is the command I can test it with? Because I have a feeling that this macro works only sometimes. For example I have a setting of log file = /var/log/samba/%m.log, and there are log files with netbios names and ip addresses too. (nbname.log, x.x.x.x.log). Any ideas would be appreciated... Kolos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netbios name resolution
I have a setting of log file = /var/log/samba/%m.log, and there are log files with netbios names and ip addresses too. (nbname.log, x.x.x.x.log). Any ideas would be appreciated... This is the behavior by design (I believe) but at least it is understandable once you know what is going on. When a client connects, the only thing you know about it is its IP address. Even if the very first thing it does is to query the network for naming related information, or to be queried by the server for its name there is still this name-less connection. You should notice that most of these files are 0 length. I know there was a better explanation of what is happening, but it came down to the fact that it was normal. -- Paul GiengerOffice: 701-281-1884 Applied Engineering Inc. Systems Architect Fax:701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netbios name resolution
Hello,
I have a setting of log file = /var/log/samba/%m.log, and there are log
files with netbios names and ip addresses too. (nbname.log, x.x.x.x.log).
This is the behavior by design (I believe) but at least it is
understandable once you know what is going on. When a client connects,
the only thing you know about it is its IP address. Even if the very
first thing it does is to query the network for naming related
information, or to be queried by the server for its name there is still
this name-less connection. You should notice that most of these files
are 0 length.
The problem is that those files are not 0 length.
For example:
$ dig vendeg.[mydomain]
[..]
;; ANSWER SECTION:
vendeg.[mydomain]. 3600 IN A 192.168.0.31
[..]
$ cat vendeg.log
[..]
[2005/04/14 15:15:57, 1] smbd/service.c:make_connection_snum(698)
vendeg (192.168.0.31) connect to service install initially as user root
(uid=0, gid=0) (pid 17536)
[2005/04/14 15:16:01, 1] smbd/service.c:make_connection_snum(698)
vendeg (192.168.0.31) connect to service kolos initially as user kolos
(uid=500, gid=100) (pid 17536)
[2005/04/14 15:16:08, 1] smbd/service.c:close_cnum(880)
vendeg (192.168.0.31) closed connection to service install
::{2227a280-3aea-1069-a2de-08002b30309d}
[..]
$ cat 192.168.0.31.log
[..]
[2005/04/15 14:59:07, 1] smbd/service.c:make_connection_snum(698)
192.168.0.31 (192.168.0.31) connect to service install initially as user
root (uid=0, gid=0) (pid 2776)
[2005/04/15 14:59:15, 1] smbd/service.c:close_cnum(880)
192.168.0.31 (192.168.0.31) closed connection to service install
[2005/04/16 18:38:24, 1] smbd/service.c:make_connection_snum(698)
192.168.0.31 (192.168.0.31) connect to service install initially as user
root (uid=0, gid=0) (pid 3346)
[2005/04/16 18:39:44, 1] smbd/service.c:close_cnum(880)
192.168.0.31 (192.168.0.31) closed connection to service install
[..]
In these log snippets the services being connected to are install in
both files, still one has the ip resolved and the other not.
Any ideas?
Thank you for the reply anyway.
I know there was a better explanation of what is happening, but it came
down to the fact that it was normal.
I understand, and this would make sense, but I suppose that's not the
case.
Thanks,
--
Tatr Kolos
Archi-data Kft.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netBIOS API for WINS
I would like to get IP adress from WINS (not from broadcast or LMHOSTS file) for given NetBIOS name using Windows netbios API (functions) - however - I can't understand what I should specifu into NBC structure - should I make socket connection to WINS server and issue NCBFIND or should I use SEND/RECEIVE to communicate directly with WINS - if later is teh case - then what chunk of data should I send and what data can I expect to receive Should I read all those RFC's or dive into nbdc code? Thanks for suggestions in advance! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios over ipsec (slightly ot)
Hi, This issue might be a slightly offtopic, but someone might have experience with it. Thanks for reading this post anyway. I have the following setup: Network 10.227.7.X is connected over a wlan (172.1.1.1 - 172.1.1.2) to network 128.1.1.X. This setup works, I have cross-subnet browsing going and I am able to login. When I enable IPSEC (raccoon (linux - freebsd)) I am still able to login and to browse the network, but I am unable to access any of the shares on the other subnet (this *does* work without ipsec). I used tcpdump to see if any packages are arriving on both ends and the server (samba 3.0.10) does seem the receive the packages and answers these packages as well, but the when having ipsec enabled the connection behave differently than without ipsec as the client seems to ask multiple times for something. I tried changing the MTU, but this does not seem the help. Maybe I am forgetting something as this setup is slightly complicated as it considers 4 firewalls (don't ask me why please ;-)), but the firewalls do not seem to be the problem as logins do work over ipsec. Regards, B. de Bruin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] netbios fw pls help
Hi There, I'm runnin Linux Debian server with samba 3.0.10 and have vpn to connect from remote subnets. The prblem is that I cant see connected PC winXP clients in the network neighbourhood. Also have problem using terminal services through linux vpn. Please anyone to help -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netbios fw pls help
Hello, nick schrieb: Hi There, I'm runnin Linux Debian server with samba 3.0.10 and have vpn to connect from remote subnets. The prblem is that I cant see connected PC winXP clients in the network neighbourhood. Also have problem using terminal services through linux vpn. Please anyone to help You have problems with IP to Name resulotion. You can user WINS for only Windows-PC-Network and DNS for all other. Please test, to type in the IP-Adresse directly. matze -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios over VPN
Hi all, First of all let me describe my vpn config. I have 3 networks and 1 host connected through OpenVPN: LAN1: LAN IP: 192.168.0.0 VPN IP TO LAN2: 10.0.0.1 VPN IP TO LAN3: 10.0.1.1 VPN IP TO HOST1: 10.0.2.1 LAN2: LAN IP: 192.168.1.0 VPN IP TO LAN 1: 10.0.0.2 LAN3: LAN IP: 192.168.30.0 VPN IP TO LAN 1: 10.0.1.2 HOST1: VPN IP TO LAN 1: 10.0.2.2 As you can see, all vpn connections are going through a LAN1 server, so any traffic between the vpn is routed through this server. The problem is that I can access any host on the vpn from everywhere (including samba shares) with the IP address but not with the netbios name. Reverse nmblookup works (nmblookup -A 192.168.0.1) meaning that netbios ports are not filtered. As I understand I must have the right settings for *remote announce* and *remote browser sync* but don't know which are these settings since I tweaked them without any luck. Or maybe there are other options that must be configured. Thanks all for your replies, Arthur -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS wildcard queries repeated by wireless access points
I am trying to resolve a problem with NetBIOS wildcard broadcast queries being relayed/repeated by around 50 US Robotics wireless access points. The APs only re-broadcast wildcard queries from our samba3 server - our numerous windows 2003 servers do not appear to use wildcard broadcast queries (if they do, they are not causing the same problems). Any help would be appreciate as this problem is causes massive network problems as all our winxp clients repeatedly reply to each repeated query. Kind regards Lee Baker The initial NetBIOS packet from the samba server: (192.168.5.200 is the samba server, 192.168.2.185 is a USR Access Point) No. TimeSourceDestination Protocol Info 3143 200.215902 192.168.5.200 192.168.5.255 NBNS Name query NB *00 Frame 3143 (92 bytes on wire, 92 bytes captured) Arrival Time: Feb 7, 2005 18:23:30.407103000 Time delta from previous packet: 91.745643000 seconds Time since reference or first frame: 200.215902000 seconds Frame Number: 3143 Packet Length: 92 bytes Capture Length: 92 bytes Ethernet II, Src: 00:0b:db:90:9f:0b, Dst: ff:ff:ff:ff:ff:ff Destination: ff:ff:ff:ff:ff:ff (Broadcast) Source: 00:0b:db:90:9f:0b (192.168.5.200) Type: IP (0x0800) Internet Protocol, Src Addr: 192.168.5.200 (192.168.5.200), Dst Addr: 192.168.5.255 (192.168.5.255) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 00.. = Differentiated Services Codepoint: Default (0x00) ..0. = ECN-Capable Transport (ECT): 0 ...0 = ECN-CE: 0 Total Length: 78 Identification: 0x (0) Flags: 0x04 (Don't Fragment) 0... = Reserved bit: Not set .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0xad87 (correct) Source: 192.168.5.200 (192.168.5.200) Destination: 192.168.5.255 (192.168.5.255) User Datagram Protocol, Src Port: 33175 (33175), Dst Port: netbios-ns (137) Source port: 33175 (33175) Destination port: netbios-ns (137) Length: 58 Checksum: 0x4190 (correct) NetBIOS Name Service Transaction ID: 0x6f69 Flags: 0x0110 (Name query) 0... = Response: Message is a query .000 0... = Opcode: Name query (0) ..0. = Truncated: Message is not truncated ...1 = Recursion desired: Do query recursively ...1 = Broadcast: Broadcast packet Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries *00: type NB, class inet Name: *00 (Workstation/Redirector) Type: NB Class: inet The packet relayed by A US Robotics Access Point: No. TimeSourceDestination Protocol Info 3151 200.216628 192.168.5.200 192.168.5.255 NBNS Name query NB *00 Frame 3151 (92 bytes on wire, 92 bytes captured) Arrival Time: Feb 7, 2005 18:23:30.407829000 Time delta from previous packet: 0.000667000 seconds Time since reference or first frame: 200.216628000 seconds Frame Number: 3151 Packet Length: 92 bytes Capture Length: 92 bytes Ethernet II, Src: 00:c0:49:a9:b8:b4, Dst: ff:ff:ff:ff:ff:ff Destination: ff:ff:ff:ff:ff:ff (Broadcast) Source: 00:c0:49:a9:b8:b4 (192.168.2.185) Type: IP (0x0800) Internet Protocol, Src Addr: 192.168.5.200 (192.168.5.200), Dst Addr: 192.168.5.255 (192.168.5.255) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 00.. = Differentiated Services Codepoint: Default (0x00) ..0. = ECN-Capable Transport (ECT): 0 ...0 = ECN-CE: 0 Total Length: 78 Identification: 0x (0) Flags: 0x04 (Don't Fragment) 0... = Reserved bit: Not set .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 63 Protocol: UDP (0x11) Header checksum: 0xae87 (correct) Source: 192.168.5.200 (192.168.5.200) Destination: 192.168.5.255 (192.168.5.255) User Datagram Protocol, Src Port: 33175 (33175), Dst Port: netbios-ns (137) Source port: 33175 (33175) Destination port: netbios-ns (137) Length: 58 Checksum: 0x4190 (correct) NetBIOS Name Service Transaction ID: 0x6f69 Flags: 0x0110 (Name query) 0... = Response:
Re: [Samba] Netbios Aliases and %L and port 445
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Bartlett wrote: | If there was, we would use it. This information is | simply no longer supplied by the client, when it talks to | port 445. Andrew's right. The only alternative is to use a multi-homed samba host (even virtual IPs) and the %i variable. If my memory serves me correctly. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB8SKyIR7qMdg1EfYRApzEAKDuBPbY61b84svTfJszJKHt0Qu0gQCfeqni C/ukPdgP5ESxj4zskPsc6So= =ww4d -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Aliases and %L and port 445
| |Andrew Bartlett wrote: | || If there was, we would use it. This information is || simply no longer supplied by the client, when it talks to || port 445. | | |Andrew's right. | |The only alternative is to use a multi-homed samba host |(even virtual IPs) and the %i variable. If my memory serves |me correctly. | | |cheers, jerry | What's the downside to 'disabling' port 445 with smb ports = ? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Netbios Aliases and %L and port 445
Running v3.0.2a-SUSE, joined to AD, all clients are XP.SP2 When smb.conf has smb ports = 139, then %L is populated with the appropriate netbios alias name as selected by the end user, and everything works as expected. When smb ports = 445 or is not specified, then %L is populated with the host name instead of the alias name. Is there a code patch for %L or an undocumented %parm to use instead to get the alias name as selected by the client (not the hosting server name)?? The reason I ask is because Netbios is still responding to the alias name, and an Ethereal sniff of simple traffic Net View \\samba-alias (after an NBTstat - R) when smb ports = 445 seems to show the alias name still being used back forth to the Samba box, and Samba itself is resolving the alias name (I don't have Disable Netbios=yes). Therefore, isn't there some way for Samba to internally pick this up and populate %L correctly? Thx in advance. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Netbios Aliases and %L and port 445
On Thu, 2005-01-20 at 20:03 -0800, David Loudon wrote: Running v3.0.2a-SUSE, joined to AD, all clients are XP.SP2 When smb.conf has smb ports = 139, then %L is populated with the appropriate netbios alias name as selected by the end user, and everything works as expected. When smb ports = 445 or is not specified, then %L is populated with the host name instead of the alias name. Is there a code patch for %L or an undocumented %parm to use instead to get the alias name as selected by the client (not the hosting server name)?? If there was, we would use it. This information is simply no longer supplied by the client, when it talks to port 445. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS across subnets
Hi all, I would like two Samba servers to be able to talk to each other via NetBIOS. The problem is that they are on two different subnets. I have enabled broadcast ping on the routers, and the servers can each ping the other subnet with no trouble. The two relevant IPs are 192.168.1.101 and 192.168.2.3. There is a T1 between two Cisco routers, and IP routing is all set up. Currently 192.168.1.x is the CORP domain. Samba PDC is acting as the WINS server. 192.168.2.x is the FURN server, and its Samba PDC is acting as its WINS server. My Windows systems in CORP can browse to the FURN domain and see systems in it. My Windows systems in FURN can browse to the CORP domain but can't see any systems in it. Neither of my PDCs can see the other, so they cannot establish a trust. Relevant settings for CORP PDC are: wins support = yes os level = 100 preferred master = yes domain master = yes remote announce = 192.168.2.255/CORP remote browse sync = 192.168.2.255 name resolve order = bcast wins lmhosts host (there is no lmhosts or host) allow trusted domains = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Relevant settings for FURN PDC are: os level = 99 dns proxy = Yes wins support = Yes wins proxy = Yes os level = 100 preferred master = yes domain master = yes local master = yes remote announce = 192.168.1.255/FURN remote browse sync = 192.168.1.255 # I put this one in to try to get it to hear the other server's broadcasts -- did not work interfaces = 127.0.0.1 192.168.2.3/255.255.0.0 name resolve order = bcast wins lmhosts host allow trusted domains = yes Both servers are 3.0.11pre1. Both are DHCP servers as well. They are pushing out netbios server settings to the clients as follows: CORP: option netbios-name-servers 192.168.1.101, 192.168.2.3; option netbios-node-type 8; FURN: option netbios-name-servers 192.168.2.3; option netbios-node-type 8; The fact that FURN is not giving out CORP as a netbios server might be significant why the users can't see CORP's computers, but it doesn't explain why the domains can't see each other. If anybody has any information on how I can make this work I would love it. I did look in Samba 3 By Example but it doesn't really go into the networking side of it at all. Thanks, Misty -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS across subnets
Misty Stanley-Jones wrote: Hi all, I would like two Samba servers to be able to talk to each other via NetBIOS. The problem is that they are on two different subnets. I have enabled broadcast ping on the routers, and the servers can each ping the other subnet with no trouble. The two relevant IPs are 192.168.1.101 and 192.168.2.3. There is a T1 between two Cisco routers, and IP routing is all set up. Currently 192.168.1.x is the CORP domain. Samba PDC is acting as the WINS server. 192.168.2.x is the FURN server, and its Samba PDC is acting as its WINS server. In my opinion, it is wrong. On one server, set: wins support = yes On the other: wins server = 192.168.5.2 # (IP of the first one) wins proxy = yes Tomek -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS across subnets
Tomasz Chmielewski wrote: Currently 192.168.1.x is the CORP domain. Samba PDC is acting as the WINS server. 192.168.2.x is the FURN server, and its Samba PDC is acting as its WINS server. In my opinion, it is wrong. On one server, set: wins support = yes On the other: wins server = 192.168.5.2 # (IP of the first one) wins proxy = yes you will also have to allow certain hosts/subnets on each server: hosts allow = 192.168.0. 192.168.5.2 127.0.0.1 Tomek -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBIOS across subnets
Misty Stanley-Jones wrote: On Tuesday 18 January 2005 10:49, Tomasz Chmielewski wrote: In my opinion, it is wrong. On one server, set: wins support = yes On the other: wins server = 192.168.5.2 # (IP of the first one) wins proxy = yes I did this, and I think it MIGHT have worked. Not sure. I get this: oink:/usr/local/samba/var/locks # net rpc trustdom establish furn Password: Could not connect to server FURNSRV Trust to domain FURN established urnsrv:/usr/local/samba/var/locks # net rpc trustdom establish corp Password: Could not connect to server CORPSRV Trust to domain CORP established How in the world do I know if it worked or not. Going to check it now. Either way those errors certainly are sending mixed signals. It only will let me connect as a guest. I don't know if that's the expected behavior -- need to read more. The more important this is being able to join a domain on a different subnet, as that is what needs to happen when I combine the two domains into one. don't know about joining a domain from another network - never tried. I only tried joining the same domain (although in a different network). This is how it works for me: In the Network neighbourhood of your windows machine you should see hosts from both networks. smbclient -L server should list hosts from each network. Another problem you might have is too restrictive firewall between the two subnets - you will see the hosts, will be able to browse, but won't be able to join the domain. Tomek -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS-Remotecache
Hi out there. I have not been able to solve the following problem yet. I configured samba-3.0.9 as LMB/PDC with correct DNS and WINS. When I log on with my Windowsbox (no matter which version) and do immidiatly an nbtstat -c on the command-line I get: snip NetBIOS-Remotecache-Namentabelle Name TypHostadresse Dauer [Sek.] - SNEAKER1C GRUPPE 192.168.10.1395 snap When I now import lmhosts.sam with: snip 192.168.10.1 hunter #PRE #DOM:sneaker snap I get the correct information: snip NetBIOS-Remotecache-Namentabelle Name TypHostadresse Dauer [Sek.] - SNEAKER1C GRUPPE 192.168.10.1-1 HUNTER 03 EINDEUTIG 192.168.10.1-1 HUNTER 00 EINDEUTIG 192.168.10.1-1 HUNTER 20 EINDEUTIG 192.168.10.1-1 snap What have I not configured correctly??? Greetings Sascha -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] NetBIOS-Remotecache
Hi out there. I have not been able to solve the following problem yet. I configured samba-3.0.9 as LMB/PDC with correct DNS and WINS. When I log on with my Windowsbox (no matter which version) and do immidiatly an nbtstat -c on the command-line I get: snip NetBIOS-Remotecache-Namentabelle Name TypHostadresse Dauer [Sek.] - SNEAKER1C GRUPPE 192.168.10.1395 snap When I now import lmhosts.sam with: snip 192.168.10.1 hunter #PRE #DOM:sneaker snap I get the correct information: snip NetBIOS-Remotecache-Namentabelle Name TypHostadresse Dauer [Sek.] - SNEAKER1C GRUPPE 192.168.10.1-1 HUNTER 03 EINDEUTIG 192.168.10.1-1 HUNTER 00 EINDEUTIG 192.168.10.1-1 HUNTER 20 EINDEUTIG 192.168.10.1-1 snap What have I not configured correctly??? Greetings Sascha -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] NetBios problem with Samba 2.x
I'm in a bit of a pickle, and I need some help. I'm forced to disable netbios on any machine that leaves the company because of how MS Exchange works over a VPN. I have Samba 2.x on two Compaq Tru64 5.x machines, each with one (public) share. With netbios enabled, the client machines can access the share with no issues. With netbios disabled, I get something like No network provider accepted the given network path. DNS is working fine - the clients resolve the Samba machines, and the Samba machines resolve the clients. I've tried stabbing at the config a few times with things like the dns proxy setting, wins proxy, wins server, security type, etc. - no luck. I have absolutely no problem with accessing my Samba 3 system from a client with netbios disabled. Anybody know what this might be? Thanks, Nate PS - Actually, I'd love to install Samba 3 on these two problem systems, but it won't compile. :/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] NetBios problem with Samba 2.x
On Fri, 2004-10-15 at 11:30 -0700, Nate Schindler wrote: I'm in a bit of a pickle, and I need some help. I'm forced to disable netbios on any machine that leaves the company because of how MS Exchange works over a VPN. I have Samba 2.x on two Compaq Tru64 5.x machines, each with one (public) share. With netbios enabled, the client machines can access the share with no issues. With netbios disabled, I get something like No network provider accepted the given network path. I don't think Samba 2 supported DNS resolution. IIRC it requires NetBIOS Name Resolution in order to correctly resolve. Can you go direct to the IP? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBios problem with Samba 2.x
-Original Message- From: Fernando Ribeiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 2004 11:54 AM To: Aaron Grewell Cc: Nate Schindler; [EMAIL PROTECTED] Subject: Re: [Samba] NetBios problem with Samba 2.x I don't think Samba 2 supported DNS resolution. IIRC it requires NetBIOS Name Resolution in order to correctly resolve. Can you go direct to the IP? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Hi, I have same problem with samba 3.0.7 :-( Well that's interesting... I don't. Can you send your smb.conf? What operating system is samba running on? Thanks -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 LPIC-2 - Advanced Linux Death the graph! Death the mouse Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] NetBios problem with Samba 2.x
-Original Message- From: Fernando Ribeiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 2004 11:54 AM To: Aaron Grewell Cc: Nate Schindler; [EMAIL PROTECTED] Subject: Re: [Samba] NetBios problem with Samba 2.x Palavras de Aaron Grewell [Fri, Oct 15, 2004 at 11:35:52AM -0700]: On Fri, 2004-10-15 at 11:30 -0700, Nate Schindler wrote: I'm in a bit of a pickle, and I need some help. I'm forced to disable netbios on any machine that leaves the company because of how MS Exchange works over a VPN. I have Samba 2.x on two Compaq Tru64 5.x machines, each with one (public) share. With netbios enabled, the client machines can access the share with no issues. With netbios disabled, I get something like No network provider accepted the given network path. I don't think Samba 2 supported DNS resolution. IIRC it requires NetBIOS Name Resolution in order to correctly resolve. Can you go direct to the IP? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Hi, I have same problem with samba 3.0.7 :-( Thanks I gave 3.0.x another shot, and although I had a lot of warnings, 3.0.7 did compile. With netbios disabled on the windows client, the share *does* load now. (yay!) -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 LPIC-2 - Advanced Linux Death the graph! Death the mouse Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] netbios name failure, wins problem?
Hi all, [EMAIL PROTECTED]:/var/log/samba# nmblookup -S PDC querying PDC on 10.0.0.255 10.0.0.4 PDC00 Looking up status of 10.0.0.4 PDC 00 - H ACTIVE [EMAIL PROTECTED]:/var/log/samba# nmblookup -S testefinal querying testefinal on 10.0.0.255 10.0.0.100 testefinal00 Looking up status of 10.0.0.100 TESTEFINAL 00 - B ACTIVE But it don't found in master-browser. [EMAIL PROTECTED]:/var/log/samba# nmblookup -M testefinal querying testefinal on 10.0.0.255 querying testefinal on 127.255.255.255 name_query failed to find name testefinal#1d [EMAIL PROTECTED]:/var/log/samba# nmblookup It don't found into wins.dat [EMAIL PROTECTED]:/var/log/samba# tail -f /usr/local/samba/var/locks/wins.dat VERSION 1 0 PDC#00 1097349014 10.0.0.4 66R PDC#03 1097349014 10.0.0.4 66R PDC#20 1097349014 10.0.0.4 66R DOMAINNAME#00 1097349014 255.255.255.255 e4R DOMAINNAME#1b 1097349014 10.0.0.4 64R DOMAINNAME#1c 1097349014 10.0.0.4 e4R DOMAINNAME#1e 1097349014 255.255.255.255 e4R [EMAIL PROTECTED]:/var/log/samba# ifconfig eth0 Link encap:Ethernet HWaddr 00:90:27:70:E7:A5 inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 10.0.0.100 is my windows workstation. My smb.conf [global] workgroup = DOMAINMANE netbios name = PDC server string = PDC security = user encrypt passwords = yes load printers = yes log file = /var/log/samba/%m.log max log size = 50 os level = 33 local master = yes domain master = yes preferred master = yes domain logons = yes admin users = fernando.ribeiro, wesley.lago logon script = %U.bat logon path = \\%L\profiles\%U wins support = yes name resolve order = wins lmhosts hosts bcast dns proxy = no # smb ports = 137 138 139 445 interfaces = 127.0.0.1 eth0 bind interfaces only = Yes ldap passwd sync = yes ldap delete dn = Yes ldap port = 636 ldap ssl = yes passdb backend = ldapsam:ldaps://ldap.domain.com.br/ ldap admin dn = cn=suporte,dc=domain,dc=com,dc=br ldap suffix = dc=domain,dc=com,dc=br ldap group suffix = ou=Grupos ldap user suffix = ou=Usuarios ldap machine suffix = ou=Computadores idmap uid = 1-15000 idmap gid = 1-15000 nt acl support = yes create mask = 600 directory mask = 0700 force directory mode = 0700 passwd chat = *New*password* %n\n *Retype*new*password* %n\n*passwd:*all*authentication*tokens*updated*successfully* socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 add machine script = /usr/local/sbin/smbldap-useradd -w %u add user script = /usr/local/sbin/smbldap-useradd -m %u delete user script = /usr/local/sbin/smbldap-userdel %u add machine script = /usr/local/sbin/smbldap-useradd -w %u add group script = /usr/local/sbin/smbldap-groupadd -p %g delete group script = /usr/local/sbin/smbldap-groupdel %g add user to group script = /usr/local/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/local/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/local/sbin/smbldap-usermod -g %g %u dos charset = UTF-8 unix charset = UTF-8 cups server = 10.0.0.11 [homes] comment = Diretorio Home browseable = no writable = yes force user = %U [profiles] path = /home/profiles read only = No create mask = 0600 directory mask = 0700 browseable = No guest ok = Yes profile acls = Yes csc policy = disable force user = %U valid users = %U @Domain Admins [netlogon] path = /home/netlogon browseable = No read only = yes [printers] comment = Impressoras path = /var/spool/samba browseable = no guest ok = no writable = no printable = yes Anyone know why? -- Fernando Ribeiro - GPG-KEY: 0x8D7255F4 Linux Counter: #273768 - ICQ: 175630330 Linux Professional Institute - LPIC-1 Death the graph! Death the mouse! Death patents! Death closed standards! http://www.nerdgroup.org http://musb.nerdgroup.org -- Grandes mentes discutem idéias; Mentes medianas discutem eventos; Mentes pequenas discutem pessoas. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netbios aliases ?
wow, not a single taker on this one !!! hi all I have a samba server acting as a domain member server providing file/print services to our SME As i want to provide users with a list of available printers for installation, i need to give them a win32 shortcut to \\samba-server\ so they can see the available printers and install as required BUT... doing so will also show them all of the available shares... not a major issue but would rather just list the printers (i am using browseable = no to hide all shares) but am now running into another problem. I'm using a web interface to smbclient to allow staff to access the file server from home. Making all shares inviable effectively makes the use of the web smbclient pointless Is it possible to use a netbiios alias and force the printers to list under the alias ? Any other suggestion welcome -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
