Ticket #1268 (closed defect: fixed)
DHCP missing NETBIOS options when PDC is enabled
| Reported by: | anonymous | Owned by: | jacalvo@… |
|---|---|---|---|
| Milestone: | Component: | base | |
| Severity: | critical | Keywords: | DHCP NETBIOS SAMBA |
| Cc: |
Description
Ebox needs to add two lines to dhcp.conf when PDC is enabled:
option netbios-name-servers 172.16.0.1; <-EBOX SERVER
option netbios-node-type 8; ### Node type = Hybrid ###
In a standard two interface setup, this is not an issue because netbios automatically looks to the default gateway (EBOX). If, however, ebox is not the default gateway, workstations will not be able to find the PDC to join the domain w/o having to manually add the WINS server interface entry at each workstation.
I tested this fairly thoroughly this evening and I would consider this a major bug for anyone using ebox as a PDC that is not the default gateway.
Cheers,
-Jim
Attachments
Change History
comment:2 Changed 4 years ago by jcanfield@…
Hmmm...I'll dig a little deeper. Your client computers are using the default windows interface setting of "Get netbios info from DHCP server" right? ...not NETBIOS over TCP/IP?
Could be a WINS issue. The only way I could get the machines to join w/o editing DHCP conf was by adding a WINS server entry on each client.
comment:3 Changed 4 years ago by jcanfield@…
I finally have things working the way I want. Here's what needs to be done:
Firstly, this error is a result of having winbind installed. The simple fix is to uninstall winbind and your domain will work just fine in broadcast mode. If, however, you are interested in running winbind this what needs to be done:
1) add the lines above to dhcp.conf.mas
2) run 'smbldap-populate' This will allow root to be the "Netbios Domain Administrator"
3) run 'smbldap-usermod -d /root -s /bin/bash root' This will fix the root account pointers.
4) restart samba and winbind
5) Join the domain locally 'net rpc join -S DOMAIN -U root%password
6) restart winbind
7) Do an anonymous domain query 'smbclient -L localhost -U%' If you see your server and shares you should be all set.
The advantages of of this config:
- Direct WINS host lookups (Reduces broadcast traffic on larger networks)
- Hostnames are matched to IP's even if they are not in DNS.
Also, running smbldap-populate will create a 'nobody' user. This might be annoying for some users. I'm not sure at this point exact what the account is used for.
comment:4 Changed 4 years ago by michael.judd@…
Just letting you know - I had the same issue and this ticket fixed the problem. I also had a separate gateway and I was having problems joining a windows XP computer to the domain. It would be great to see this in the core. I'm on: 0.11.100
comment:5 Changed 4 years ago by juruen@…
Micheal,
Did you have winbind installed on the eBox machine when you tried to add the machine to the domain?
If you did, that's probably the reason why you couldn't add the machine to the domain.
comment:6 Changed 4 years ago by michael.judd@…
No - there's no winbind installed as far as I can see (no /etc/init.d/winbindd)
comment:7 Changed 4 years ago by vlado@…
Still getting: root@server01:/# net rpc join -S DOMAIN -U root%pass Unable to find a suitable server Unable to find a suitable server
comment:8 Changed 4 years ago by nefarius@…
I had exactly the same problem. After I put the line
option netbios-name-servers <server-ip>
into dhcpd.conf my Windows XP Pro (x64) Workstation found the PDC and i was able to add the workstation to the domain. The only problem now: if i change the DHCP-Options with the web-interface it's overwritten ;)
I used a complete fresh eBox installation (version 1.2) and only one iface (eth0) to test it.
IMHO it would be better to add an option-field to the DHCP-Site like
Common options / Primary WINS Server: local eBox DNS
or something like that. (btw. sry for my english...)
comment:10 Changed 3 years ago by ejhernandez@…
- Status changed from new to closed
- Resolution set to fixed
comment:11 in reply to: ↑ description Changed 3 years ago by anonymous
Replying to anonymous:
Ebox needs to add two lines to dhcp.conf when PDC is enabled:
option netbios-name-servers 172.16.0.1; <-EBOX SERVER
option netbios-node-type 8; ### Node type = Hybrid ###
In a standard two interface setup, this is not an issue because netbios automatically looks to the default gateway (EBOX). If, however, ebox is not the default gateway, workstations will not be able to find the PDC to join the domain w/o having to manually add the WINS server interface entry at each workstation.
I tested this fairly thoroughly this evening and I would consider this a major bug for anyone using ebox as a PDC that is not the default gateway.
Cheers,
-Jim
Can you help me in building a server ebox reciever ??
What way?? How can I make my receiver work through code?
thanx
I think we are missing something here. I always test the PDC configuration in my local network with a machine that only has one interface. My test machine is not working as a gateway, and I have added windows machines to the domain successfully. So I'm pretty sure it should be something else that we are missing...