Displaying 4 results from an estimated 4 matches for "preshs".
Did you mean:
presas
2007 Jan 03
0
error upon logging out of XP clients
I have a domain controller called preshs. I have a few Windows XP
computers using linksys wireless cards and a wireless access point that
all connect to preshs. The network works fine. Logging in produces no
errors, however when a person logs out of an XP machine they get the
following error:
Windows cannot copy file C:\Documents...
2008 Apr 08
1
unable to compile samba 3.0.28a on RHEL 5.1 i386
...lt output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
error: Bad exit status from /var/tmp/rpm-tmp.12141 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.12141 (%build)
makerpms.sh: Done.
and config.log:
[root@preshs RHEL]# cat
/usr/src/redhat/BUILD/samba-3.0.28a/source/config.log |more
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.59. Invocation command line was...
2008 Apr 14
0
problem with user nobody and net groupmap
...etOrgPerson
objectClass: posixAccount
objectClass: top
objectClass: shadowAccount
objectClass: hostObject
userPassword:: xxxxxxxxxxxxxxxx
shadowLastChange: 13966
shadowMax: 99999
shadowWarning: 7
loginShell: /bin/sh
uidNumber: 65534
gidNumber: 65534
host: roark
host: archives3
host: arrowhead
host: preshs
host: wmounds
host: manship
host: welty
homeDirectory: /home
gecos: Nobody
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
[root@roark samba]#
[root@roark samba]# ldapsearch -D
'cn=Manager,dc=mdah,dc=state,dc=ms,dc=us' -b
"cn=nobody,ou=Group,dc=mdah,d...
2008 Dec 16
3
Vista roaming profiles...
Hi everybody,
after many weeks of searching/trying, I still can't manage to get vista to use/save roaming profiles with samba as PDC...
It has apparently worked a few times in the beginning since the profiles directories are populated.
Could it be related to a Vista update or SP1?
Here's what I did so far:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]