Hi,
I have setup an dhcp server wich allows ICS, and a samba server as a PDC.
I can access the shares from windows if I type the server Ip (ej. \192.168.0.1), however if if write the address (ej. \dbaserver) I cannot access them.
If I type ping dbaserver on a command prompt, it returns 127.0.0.2 not 192.168.0.1, what could be wrong. I asume because of this I cannot join the domain also.
thanks,
Juan Solorzano
On Thu January 14 2010 09:36 am, juansolorzano wrote:
>
> Hi,
> I have setup an dhcp server wich allows ICS, and a samba server as a
> PDC.
> I can access the shares from windows if I type the server Ip (ej.
> \192.168.0.1), however if if write the address (ej. \dbaserver) I
> cannot access them.
> If I type ping dbaserver on a command prompt, it returns 127.0.0.2 not
> 192.168.0.1, what could be wrong. I asume because of this I cannot join
> the domain also.
>
> thanks,
>
> Juan Solorzano
>
>
Juan;
Is nmbd running? Check with:
ps -A |grep nmb
If nmb is running, check that the firewall is open for “netbios server”
If nmb is not running, enable it, nmbd(nmb), in YaST ->System->system services
for run level 3 and 5 and open the firewall for the netbios server.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Hi,
the nmb is running I get
:~> ps -A | grep nmb
2643 ? 00:00:02 nmbd
2644 ? 00:00:00 nmbd
Firewall is open for netbios server
Some of the machines I get the correct 192.168.0.1, and on others I get 127.0.0.2, specially those that are not in the domain (ie. windows home on laptops).
My smb.conf is:
global]
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = Yes
domain master = Yes
include = /etc/samba/dhcp.conf
local master = Yes
netbios name = dbaserver
os level = 65
passdb backend = tdbsam
preferred master = Yes
security = user
wins support = Yes
workgroup = dbanet
log file = /var/log/samba/%m
logon drive = w:
logon home = \dbaserver%U
logon script = dbauser.bat
admin users = administrador, jsolorzano
[homes]
comment = Home Directories
valid users = %S
read only = no
browseable = no
create mask = 0750
follow symlinks = yes
wide links = yes
[netlogon]
comment = Network Logon Service
path = /media/disco02/data/logon
[proyectos]
comment = proyectos grupodba
path = /media/disco03/proyectos
read only = no
create mask = 0750
directory mask = 0774
force create mode = 0660
force directory mode = 0770
,
regards
On Fri January 15 2010 10:06 am, juansolorzano wrote:
>
> Hi,
> the nmb is running I get
> :~> ps -A | grep nmb
> 2643 ? 00:00:02 nmbd
> 2644 ? 00:00:00 nmbd
>
> Firewall is open for netbios server
>
> Some of the machines I get the correct 192.168.0.1, and on others I get
> 127.0.0.2, specially those that are not in the domain (ie. windows home
> on laptops).
>
> My smb.conf is:
> global]
> add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody
> -s /bin/false %m$
> domain logons = Yes
> domain master = Yes
> include = /etc/samba/dhcp.conf
> local master = Yes
> netbios name = dbaserver
> os level = 65
> passdb backend = tdbsam
> preferred master = Yes
> security = user
> wins support = Yes
> workgroup = dbanet
> log file = /var/log/samba/%m
> logon drive = w:
> logon home = \dbaserver%U
> logon script = dbauser.bat
> admin users = administrador, jsolorzano
<snip>
> ,
> regards
Juan;
First: Check that all the windows machines are set to
domain/workgroup “dbanet” and that they all have the win server set to point
to the PDC (192.168.0.1 in your case). (I’m guessing this is ok but check
anyway.)
Second: When non domain computers have the same workgroup name as the domain,
under some circumstances they will “steal” master browsing from the PDC. You
can check this in a number of ways. Check the contents of:
“/var/log/samba/log.nmbd” check that nmbd is the master browser for your
network. If there is nothing pertinent in this file add the following to
the [global] section of /etc/samba/smb.conf:
log level = 1
Restart smb and nmb and check again. After the restart, your network may be OK
for a while until the rogue machine grabs the master browsing again.
You can also check the contents of: /var/lib/samba/browse.dat, the master
browser list. This is a simple text file and you want to make sure all the
computers are listed. While your at it check: /var/lib/samba/wins.dat, Win
server data, to see if all the computers are listed. You should also see
entries <domain name>#1c pointing to your PDC and <domain name>#1b pointing
to the master browser ( this should also be your PDC).
If you discover there is one (or more) rogue machine(s) that is (are) becoming
the Master Browser you can disable this with a regedit. Look at:
HKLM\System\Current ControlSet\Services\Browser\Parameters change the value
of “MaintainServerList” to No. This prevents the machine from becoming the
master browser.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Did you set up the DHCP server to offer the wins server to the clients?