search for: andruczyk

Displaying 5 results from an estimated 5 matches for "andruczyk".

2002 Oct 17
2
memdisk issues with 3com cards
...isk and bootup and logon great. Just the 3coms give me trouble. Has anyone seen this? or know how to get around this issue? (using the floppy for all these machines is troublesome as some don't have floppy drives (laptops) and others have floppy disk locks in place._ Thanks... ===== Dave J. Andruczyk __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
2002 Sep 20
3
"@" doesn't work in the NT domain name
I am part of a large worldwide Active Directory and all of our individual site NT domain names have an ampersand symbol in them (for example: VWS@ROCHESTER) Samba 2.2.6pre2 and older won't join this domain name, or allow connections to it from users in this domain. The logs state that the domain name is "VWS_ROCHESTER", the code is squashing the @ to an _ causing all
2002 Jul 18
1
CRITICAL can't copy files to samba volumes
I've set the perms on the vlumes as wide open as possible.. 2k and Win98 give different errors. When trying to copy a local folder (With files in it) to the smaba share I get: You may not be able to to access files created in the folder \\samba-server\software\new folder\scripts Do you want to continue Yes No Win2k says "Cannot copy FOLDERNAME: The specified network name is
2002 Jul 18
2
The specified network name is no longer available: HELP
I've been tearing my hair out trying to get this to work. Problem: Samba versions 2.2.4 and 2.2.5, running on mandrake 8.2 and 8.1 respectively, both with XFS (the mdk 8.2 machine is using a STOCK kernel 2.4.18-6mdk), the mdk 8.1 machine is using a stock 2.4.18 + xfs 1.1 patch. Windows 2000 SP2 client tries to copy a folder with files in it to the share. Copy seems to start but ends rapidly
2002 Jul 19
0
SOLUTION :to can't copy files to samba volume
I've managed to fix the problem with copying to a samba share resulting in the "server is no longer available message". The problem was caused by the SGI libacl-2.0.9 upgrade. Seems like SGI broke some of the attr function calls from the acl lib into the attr lib. Since samba binaries tended to be linked ONLY to libacl, and not libattr this caused issues with samba. My solution on