search for: testpc2

...which works just fine. I've now assigned Unix properties to another account. When I run 'wbinfo -i' on the AD server I see the correct info: root at dc1:~# wbinfo -i test OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false When I try the same thing on the client I get: root at testpc2:~# wbinfo -i test test:*:4294967295:4294967295::/home/test:/bin/bash I also tried some other accounts and got the same result. The only account that seems to work fine is my own account (and no it is not in /etc/passwd :-) Any idea what might be wrong? smb.conf on the client: [global] s...

...her account. When I >> run 'wbinfo -i' on the AD server I see the correct info: >> >> root at dc1:~# wbinfo -i test >> OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false >> >> When I try the same thing on the client I get: >> >> root at testpc2:~# wbinfo -i test >> test:*:4294967295:4294967295::/home/test:/bin/bash >> >> I also tried some other accounts and got the same result. The only >> account >> that seems to work fine is my own account (and no it is not in /etc/passwd >> :-) >> >> Any...

...assigned Unix properties to another account. When I > run 'wbinfo -i' on the AD server I see the correct info: > > root at dc1:~# wbinfo -i test > OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false > > When I try the same thing on the client I get: > > root at testpc2:~# wbinfo -i test > test:*:4294967295:4294967295::/home/test:/bin/bash > > I also tried some other accounts and got the same result. The only account > that seems to work fine is my own account (and no it is not in /etc/passwd > :-) > > Any idea what might be wrong? > >...

...Is this correct behavior? I then changed bldg1's logon path from logon path = \\%L\profiles\%U to logon path = \\bldg1\profiles\%U and re-logged in, but the profile was still stored on gomer. Why is that? If I have another BDC on another subnet, like bldg2 w/ ip of 10.8.11.2 and another testpc2 w/ IP of 10.8.11.32, and have its WINS set to 10.8.11.2 and log in, what would happen? Would a roaming profile be stored on bldg2 because its on another subnet, or would the profile also be on gomer? I'd like the profiles to be subnet specific because we have multiple sites connected by T...

...assigned Unix properties to another account. When I > run 'wbinfo -i' on the AD server I see the correct info: > > root at dc1:~# wbinfo -i test > OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false > > When I try the same thing on the client I get: > > root at testpc2:~# wbinfo -i test > test:*:4294967295:4294967295::/home/test:/bin/bash > > I also tried some other accounts and got the same result. The only account > that seems to work fine is my own account (and no it is not in /etc/passwd > :-) > > Any idea what might be wrong? > >...

...unt. When I > run 'wbinfo -i' on the AD server I see the correct info: > > root at dc1:~# wbinfo -i test > OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false > > When I try the same thing on the client I get: > > root at testpc2:~# wbinfo -i test > test:*:4294967295:4294967295::/home/test:/bin/bash > > I also tried some other accounts and got the same result. The > only account > that seems to work fine is my own account (and no it is not in > /etc/passwd >...

...run 'wbinfo -i' on the AD server I see the correct info: >> >> root at dc1:~# wbinfo -i test >> OFFICE\test:*:10000:500:test:/home/OFFICE/test:/bin/false >> >> When I try the same thing on the client I get: >> >> root at testpc2:~# wbinfo -i test >> test:*:4294967295:4294967295::/home/test:/bin/bash >> >> I also tried some other accounts and got the same result. The >> only account >> that seems to work fine is my own account (and no it is not in >>...