Hi, i tried with settings 2 again (2 interfaces, local first, then broadcast) and did the following:
1. remove my pc from the domain 2. restarted client pc 3. rejoined pc to the domain 4. restarted client pc Now the script starts ! Has anyone seen this behaviour too? I think the settings are now correct. Can anyone confirm that? Thanks, Benedict > Hi, > > > I moved my samba to a vserver. My smb.conf is attached below. > Samba works ok, i can see my drives & i can access the drives > like \\hel\benedict from my windows xp machine to. > > The only problem i have and that is different from when samba was > running on the host, is that the netlogon isn't working. > My logon script isn't run anymore. With the same config (well, i have to > change the hostnames & ip's) it works when run from the host. > > I'm fairly certain it has to do with how i set up the ips. > I've tried the following scenarios and i couldn't get it to work. All > configs are related to the interfaces directory. > Host has 2 ip's, eth0 192.168.0.2 & eth1 192.168.1.1. > eth1 deals with the lan so this is the important network for samba. > > 1. 1 interface only > 0: > ip: 192.168.1.26 > dev: eth1 > name: hel > bcast: 192.168.1.255 > prefix: 24 > > As i said, it all works except the logon isn't working (the samba > machine even shows up in the networkneighborhood after a while) > > 2. 2 interfaces, local first, then broadcast > 0: > ip: 192.168.1.26 > dev: eth1 > name: hel > bcast: 192.168.1.255 > prefix: 24 > > 1: > ip: 192.168.1.255 > nodev: empty > > I couldn't even logon to the domain anymore. > > 3. 2 interfaces, broadcast first, then local > 0: > ip: 192.168.1.255 > nodev: empty > > 1: > ip: 192.168.1.26 > dev: eth1 > name: hel > bcast: 192.168.1.255 > prefix: 24 > > smbclient in vserver hel only worked when using the ip address of the > server instead of the name to connect. > Logon to the domain worked but again no logon script that ran. > > iptables lets all through that needs to go through so that isn't the > problem. I even tried to set bcapabilites for testing and that didn't > solve a thing. > > Any ideas? > > Thanks, > Benedict <snip> _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
