Displaying 4 results from an estimated 4 matches for "winy2k".
Did you mean:
win2k
2002 May 16
9
WinY2k Access Denied on Printing
I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver
built with --with-ldapsam. The clients are either win9x or WinY2k.
Authenitcation, etc... all works great.
But print sharing is a real pain. Under 2.2.1a printing worked great, but our
VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial
testing of 2.2.4 made it seem like everything worked. But eventually WinY2k
users can'...
2003 Oct 20
1
Win9x Cannot Find Server, WinY2k Can
...the name of "sardine" in order to connect to any
resources. They can resolve the name of the PDC ("littleboy") and print
to printer queues defined on the PDC but they can't find sardine.
Restarting the smb service fixes it for a little while but then the
problem returns. WinY2k workstations are always able to connect without
any errors. I've also stopped smb, removed /var/cache/samba/wins.dat,
and restarted smb - but the problem still returns.
I don't see any error messages in the logs.
Any pointers or suggestions would be most welcome.
2003 Oct 30
0
Can't login into PDC, Running Samba 2.2.7 on Suse 8.2
...R, HERE'S THE
KICKER, AFTER I RESTART THE WORKSTATIONS AS INSTRUCTED BY WINDOWS, I
CANNOT LOGIN INTO THE DOMAIN. I get 2 separate error messages for XP and
Y2K and I can only log in to the workstation locally.
WinXP Error:
The system cannot log you on because the domain POLC is not available.
WinY2K Error: The system cannot log you on to this domain because the
system's computer account in its primary domain is missing or the
password on that account is incorrect.
Checked log.smbd and found the following.
[2003/10/30 11:08:04, 3] smbd/reply.c:reply_sesssetup_and_X(858)
Domain=[] Nat...
2002 Aug 20
2
Upgrade broke file locking
...se by bob'. Sure enough smbstatus -L shows the file locked by bob, but bob is
the one that can't open it. And if bob shuts down his computer the lock seems
to hang around for a bit. And the same file will continue to exhibit the same
behavior, even after reboots of the client PC (mostly winY2k boxes). Has anyone
seen anything like this?
System
-------------------
Distro: RedHat 7.3
Kernel: 2.4.18-3smp
Glibc: 2.2.5-39
GCC: 2.96-112
GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
GCC: gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)
Samba:
-------------------...