[Samba] RE: Disable roaming profiles per user
Dear Paul, We recently set up a mandatory roaming profile for the domain admin in samba and *that* might fit your needs. By renaming the NTUSER.DAT file in the root of the user's profile directory to NTUSER.MAN, changes made to the local profile after logging on from the domain are not copied back up to the 'profiles' folder. It was necessary for us to do this because sloppy admins were saving patches, software, etc. on the desktop of the domain admin account - the desktop is copied up to the profiles directory, and when the domain admin logged on to a machine that hadn't been accessed in a while, it took a VERY VERY LONG time to copy down the extremely large user profile. Irritating for all of us windows admins. Anyway, in your case, I'd delete the roaming profiles of the 4 users you want to disable roaming profiles for, recreate the profiles - with a barebones setup, and then rename NTUSER.DAT to NTUSER.MAN in the profiles folders belonging to those users. HTH, Sam Barasch Computer Systems Support Dept. of Biostatistics Universit of Wisconsin - Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] RE: XP Joining domain
Hi Derek. What's interesting about these errors is that the Join seems to succeed, but that the machine password in the smbpasswd file is not modified. We're still using the 2.2.x stream of samba, and I've been meaning to try the 3.0.x versions, but haven't gotten around to it yet. I hope my suggestions still apply to the version of samba you're using. At first blush, it looks like you're having some permissions problems editing the smbpasswd file and creating the machine account passwd for the XP machine joining the domain. Let me review items you've tried 1) Manually creating unix account and adding machine account to smbpasswd file with smbpasswd -am xptest$ (your unix passwd entry looked fine) 2) The unix root account has an smbpasswd, and you're using that when prompted. (We've never been able to get domain admins to join machines (because smbpasswd file is writable by only root) 3) It does look like the smbpasswd machine account has been disabled - have you tried re-enabling it and rejoining the machine? Smbpasswd -e xptest$ Because the smbpasswd file doesn't get modified, I suspect some kind of permissions problem. When trying to join the domain, have you already connected to the samba server using a different set of credentials? In our version of samba, only one set of credentials is allowed - try doing a 'net use /delete *' (or something like that) from the PC to be sure you haven't unwittingly opened a connection to the samba server before trying to join the domain. Good luck-- Sam Barasch Computer Systems Support Dept. of Biostatistics University of Wisconsin in Madison -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] >> Behalf Of Derek Harkness >> Sent: Monday, June 07, 2004 11:20 AM >> To: [EMAIL PROTECTED] >> Subject: [Samba] XP Joining domain >> >> >> I'm attempting to join a Samba 3.0.4 domain on a Debian linux box, >> with >> a Windows XP client. >> >> Problems >> 1) Can only get the join to work if I use the root account. On Win2k >> I >> can use any account in the Domain Admins group. >> 2) The join succeeds, the unix account and the smb account are created >> but the smb account is disabled, and the password contains all s. >> Joining the domain works fine from Win2k. >> >> I've tried adjusting the Signing entries. I tried manually creating >> the machine accounts, and I get a can't access machine account error >> on >> login. >> >> Any thoughts? >> >> Thanks! >> Derek >> >> "This world is a comedy to those who think and a tragedy to those who >> feel." >> >> > My lack of knowledge is only exceeded by my lack of concern. > --Anonymous GE Engineer -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Optimizing Samba
Hi Robert. We're big ACT users and haven't noticed the type of problems that you're talking about - in any version of Samba. What size are your ACT databases - in record # and MB's? What version of Samba are you running? How are oplocks configured on your Samba PDC? Is there any difference in erformance across client platforms? How about posing a snippet of smbstatus - u ? I'm just a little curious, because the ACT package is one that we use a lot. -Sam At 10:23 AM 12/27/2002 -0500, Robert Adkins wrote: Hello All, I have put together a Samba PDC for a mixed Bag of Windows Client workstations. We have a few Windwos 9x, some Win NT 4.0 and a handful of Windows 2000 workstations. The server is operating fine as a PDC for all workstations, all the permissions are properly set and things are running mostly smoothly. There are a few things that are somewhat slow moving on the network. For example, a few users utilize ACT! 4.0 and ACT! 6.0 for contact management. Their contact Databases are located on the server, in order to keep them available if they need to change workstations and also for back-up purposes. The only issue they have is when exiting the application both versions of ACT! take an inordinate amount of time to do their shutdown. I believe that both versions reset some lock files and do a few other minor things to the datafiles during the closing process. On our old server, those applications closed down almost instantly. So, what I need is some optimization ideas in order to speed up those close writes to the ACT! DC Files. Another minor issue that I have is that sometimes in Windows Explorer, some files aren't listing properly. The files are all named numerically and normally all list in ascending order. (ie. 12319 comes first, 12320 comes second and so on...) On occasion, one or more files will show up out of order, always at the end of the file listing. (ie. The last file created and numbered is 12319, but the last file in the listing is shown as 11245.) I think that this might have to do with it being accessed by a Windows 98 First Edition system that has occasion to open some of those files. The workstation that normally creates and accesses those files is a Windows 2000 Professional workstation. Any suggestions or help is greatly appreciated. Thanks! Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplocks and samba 2.2.7
Yeah, we've got kind of a big system too - our one samba server provides services for users in three buildings on campus, and no one from our support team (about 7 end-user support staff members) has heard of any oplock problems since our upgrade. It could be that something else has changed, network-infrastructure-wise , but I really doubt it. Anyway, I ask every year for the department to send me to the Samba conference - is it going to be in Germany again? At 08:33 PM 12/12/2002 +, [EMAIL PROTECTED] wrote: On Thu, Dec 12, 2002 at 02:27:26PM -0600, Sam Barasch wrote: > About two months ago our sysadmin upgraded to samba 2.2.7 and we have not > had any oplock problems since. > > A heartfelt thanks from the University of Wisconsin in Madison to the Samba > team for all their hard work. > > If our hundreds of users understood what was going on behind the scenes, > they'd be thanking you too. Wow - thanks ! I only ever hear about problems people have with oplocks so it's occasionally nice to hear the code actually *does* work :-) :-). Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] oplocks and samba 2.2.7
About two months ago our sysadmin upgraded to samba 2.2.7 and we have not had any oplock problems since. A heartfelt thanks from the University of Wisconsin in Madison to the Samba team for all their hard work. If our hundreds of users understood what was going on behind the scenes, they'd be thanking you too. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 2.2.5 as Wins-Server with Win XP workstation.
Mr. Glatzel. I don't think I understand your problem fully. However, I will try to help. So, if you point the WINS settings on your XP clients to be the IP address of your samba server, you are unable to logon to the samba domain, yet when you do not direct the WINS services on the XP clients to point at the samba server, you are able to logon to the samba domain? If that is the case, I must say, it is quite peculiar. Not that the Micro$oft side error messages are very informative, but do you get an error message on the XP clients when logging into the domain? Are you using the lmhosts file at all? -Sam At 01:30 PM 11/8/2002 +0100, Glatzel Tino wrote: Hello, if i set my samba-server as wins-server in the XP wokstation, the workstation can't find the samba DC for domainlogon. The DC and the Wins are on the same system. Without the wins-settings on the XP-box, domainlogons are possible. This problem is not with a NT 4.0-workstation. Can anybody help me ?? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplock problems
Eddy, One more thing, I have anecdotal evidence (not emperical) that we've had fewer oplock problems with our computers that are configured to use the samba server as their Domain Controller. Obviously, there is some administrative over head involved with that. If you are able to run some experiments, I'd appreciate some feedback about what worked best for you. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplock problems
Eddy, As you have noticed, there is currently no fix (please correct me if I'm wrong) for the oplock problems you're experiencing. the oplock errors are definitely related the performance problems your customers are complaining about. oplocks are 'opportunistic locks' in which the client machine already has the file locked and all changes are made in a cached copy of the file on the client. When oplocks work correctly, the client periodically flushes the locally cached copy of the data file back to the server. When they don't work correctly, the kind of errors that you and your customers are noticing occur. The following is an exerpt from a message posted here by Mr. Jeremy Allison, a key member of the samba development & production team: Also, something Jeremy posted to the list a few days ago: Ok, as promised, a brief explaination of oplocks, share modes and locking. When a client opens a file it can request an "oplock" or file lease. This is (to simplify a bit) a guarentee that no one else has the file open simultaneously. It allows the client to not send any updates on the file to the server, thus reducing a network file access to local access (once the file is in client cache). An "oplock break" is when the server sends a request to the client to flush all its changes back to the server, so the file is in a consistent state for other opens to succeed. If a client fails to respond to this asynchronous request then the file can be corrupted. Hence the "turn off oplocks" answer if people are having multi-user file access problems. Unless the kernel is "oplock aware" (SGI IRIX and Linux are the only two UNIXes that are at the moment) then if a local UNIX process accesses the file simultaneously then Samba has no way of telling this is occuring, so the guarentee to the client is broken. This can corrupt the file. Short answer - it you have UNIX clients accessing the same file as smbd locally or via NFS and you're not running Linux or IRIX then turn off oplocks for that file or share. "Share modes". These are modes of opening a file, that guarentee an invarient - such as DENY_WRITE - which means that if any other opens are requested with write access after this current open has succeeded then they should be denied with a "sharing violation" error message. Samba handles these internally inside smbd. UNIX clients accessing the same file ignore these invarients. Just proving that if you need simultaneous file access from a Windows and UNIX client you *must* have an application that is written to lock records correctly on both sides. Few applications are written like this, and even fewer are cross platform (UNIX and Windows) so in practice this isn't much of a problem. "Locking". This really means "byte range locking" - such as lock 10 bytes at file offset 24 for write access. This is the area in which well written UNIX and Windows apps will cooperate. Windows locks (at least from NT or above) are 64-bit unsigned offsets. UNIX locks are either 31 bit or 63 bit and are signed (the top bit is used for the sign). Samba handles these by first ensuring that all the Windows locks don't conflict (ie. if other Windows clients have competing locks then just reject immediately) - this allows us to support 64-bit Windows locks on 32-bit filesystems. Secondly any locks that are valid are then mapped onto UNIX fcntl byte range locks. These are the locks that will be seen by UNIX processes. If there is a conflict here the lock is rejected. Note that if a client has an oplock then it "knows" that no other client can have the file open so usually doesn't bother to send to lock request to the server - this means once again if you need to share files between UNIX and Windows processes either use IRIX or Linux, or turn off oplocks for these files/shares. Hope this is clear :-). Jeremy. At 04:34 PM 10/29/2002 +0100, [EMAIL PROTECTED] wrote: We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11 fileservers. Our customers are complaining about slow response on the opening/closing of files in office/excel etc. In the samba log file we see the following messages : [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file My Documents/servers.doc (dev = 40220001, inode = 229991, file_id = 240). [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(833) oplock_break: client failure in oplock break in file My Documents/servers.doc [2002/10/29 09:03:27, 0] ../source/smbd/reply.c:(4387) reply_lockingX: Error : oplock break from client for fnum = 14026 and no oploc k granted on this file (My Documents/servers.doc). We found out that these messages correspond with the slow response that our users are seeing. I've searched the samba archive and there are more people having these messages. The solutions I found were : - You may have a netwerk problem ( which is NOT the case in our situation ) - Turn oplocks
Re: [Samba] domain logon problem - FreeBSD PDC w/ win2k pro and winxp pro
Mr. unix rookie, Have you applied the requiresignorseal registry hack? -Sam At 11:20 AM 10/21/2002 -0700, Unix Rookie wrote: for some reason, i cannot logon to my domain. i've created user accounts... and i was able to establish a connection between the samba server (my PDC) and my workstations by logging in as "root." however now when i try to logon it gives the following error message: "Logon Message The system could not log you on. Make sure your User name and domain are correct, then type your password again. Letters in the passwords must be typed using the correct case. Make sure that Caps Lock is not accidently on." i've created both system accounts and used smbpasswd -a to establish the accounts. the odd thing is that i can connect to the samba server if i look for it using the search feature and then type my username/password. as always, any and all help will be greatly appreciated. __ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplock_break problem
Dominic, It is possible to turn off oplocks ( and level 2 oplocks ) to prevent this problem. We found that performance degraded so severely that we needed to turn oplocks back on. To turn off oplocks for all of your samba shares, add the following parameters to your [global] settings in smb.conf oplocks=no level2 oplocks = no I assume there is a lot of development going on in this area for the next version of samba, but I don't know for sure. Good luck, Sam At 09:25 AM 10/2/2002 -0400, Dominic Saindon wrote: >Hi, > >I compiled and installed Samba version 2.2.2 on Solaris 2.6 and I have the >following problem: >On certain Windows stations, there is a delay of 2 minutes to open a file. >And in the log of Samba for this station, I have the following result: >[2002/09/30 11:03:02, 0] smbd/oplock.c:oplock_break(786) >oplock_break: receive_smb timed out after 30 seconds. >oplock_break failed for file S380710.tif (dev = 1540008, inode = 24572). >[2002/09/30 11:03:02, 0] smbd/oplock.c:oplock_break(859) >oplock_break: client failure in oplock break in file S380710.tif >What can I make to correct the problem. >Thank you. >_/\___ >Dominic Saindon >Analyste en système > >COGNICASE (Canada) inc. >2144, rue King Ouest, bureau 240 >Sherbrooke (Québec) J1J 2E8 >Tél. : (819) 564-1199, poste 2282 >Téléc. : (819) 564-0868 > >Courriel : [EMAIL PROTECTED] > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: OT [Samba] Issue regarding timestamp mismatch
Bhatt, It sounds like you may need to load some unix compatibility tools (I've used interix to do this) on the NT machine, tar up the directory structure you intend to use, and untar it onto the unix box. My past experience is that this procedure totally hoses the UIDs and GIDs of the files but leaves the date stamps intact. If your NT and unix environments are more closely aligned than mine were, you may have better outcomes with the UIDs & GIDs on the files. Good luck, Sam At 03:06 PM 6/13/2002 +0100, Bhatt Gururaj wrote: >Hi, > > We have the SAMBA server installed for UNIX box. > (SWAT having 2 daemons - smbd and nmbd) > So user can access the UNIX directories through Windows NT. > > While copying any of the files from WINDOWS NT explorer to > NFS shared directory, the modify date/time automatically becomes > the current date/time, irrespective of the original file's modify > date/time. > > How do I retain this modify date/time to the original file's > date/time ? > >Regards, >Gururaj Bhat > > >= >This electronic message contains information from the mmO2 plc Group >which may be privileged or confidential. The information is intended to be >for the use of the individual(s) or entity named above. If you are not the >intended recipient be aware that any disclosure, copying, distribution or >use of the contents of this information is prohibited. If you have received >this electronic message in error, please notify us by telephone or email >(to the numbers or address above) immediately. >= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Open a W2000 Session in a domain
Joyce, It sounds like there is a disconnection between the listing in the unix passwd file for the w2000 computer and the listing in the smbpasswd file for the w2000 computer. Try deleting the listing for the computer in the smbpasswd file and re-adding it with the command # smbpasswd -am $ Good luck, Sam At 03:28 PM 6/5/2002 +0200, Joyce LAMBERT wrote: >Hello > >I am working on a Red Hat 7.1 with a samba 2.2.4 server. > >All is good i can configure my W2000 computer for the domain, but when he >restart enable to join the domain always the same message > >"le compte systeme de l'ordinateur dans son domain principal est manquant" >Yes I'm french > >So in english it's somthing like this "your computer is unkown by the >primary domain" but i have done an account for the pc with is name and >with a $ like i have show on the doc. > >Please I need some help -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Slightly OT: Conference this year?
> > >The SambaXP conference was wonderful - very well attended (better than >the Microsoft/NetApp sponsored CIFS conferences). I keep meaning to >write up a conference report and post it on Samba.org (but no time >yet). > >We're hoping the SerNet will sponsor and run the next one (as >they did such a good job this year). > >It'll be in Germany though. > >Jeremy. I'd love to go. I'll ask my department for funding. If that falls through, I'll ask my wife for funding. :-) -Sam -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Slightly OT: Conference this year?
Hi. Our department at the university has been using samba since at least 1996. We love it. Is there another conference scheduled for this year? Know where it will be? How did the last one go? --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [samba] - Domain Users and Windows 2000... Help
Hi Matt. I've had some success adding the 'authenticated users' group to the powerusers group. I think that the 'authenticated users' group consists of all users who authenticate against the domain. If authenticated users is added to the local powerusers group, it may give you what you're looking for. Again, my experiments with this are rather incomplete - I'd like to see how it works for you. I'd also be interested in a XP pro setting. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison At 03:42 PM 5/23/2002 -0500, Matt Lung wrote: >Can someone please tell me if it is possible to add a group on a linux PDC >running Samba 2.2.4 to a windows 2000 clients local "Power Users Group" or >any of the local windows 2k groups. I want certain people to be in the >Power Users Group on 2K, but I don't want to have to add each domain user >individually to that local win2k group, I want to add a domain group to >the win2k group. Right now all I see are domain users when I try and >populate a 2K local group and I'm wondering if it is possible at all to >even add a domain group to a local win2k group if anyone can provide >me with an answer I'd appreciate it. > >Thanks, >Matt Lung -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba encrypt passwd
Chimin yen, It sounds like you need an encrypted password entry in the encrypted password file. Take a look at the entry in the smbpasswd file. If it looks like user:322:::Samba User:/u/user:/bin/csh With all X's as the third and forth components of the entry (delimited by colons) you need to assign an encrypted password to the user by executing (as root) 'smbpasswd user' (don't use quotes) Good luck, Sam At 11:54 PM 5/20/2002 -0700, chimin yen wrote: >Hi, > > I have samba installed on my Linux system >(Red Hat 7.2), and Windows 98 on another PC >as a Samba client. Samba works great >if PlainTextPassword is enabled. However, if >PlainTextPassword is disabled on Windows client, >connection to the Samba shares no longer accepted. > > I believe I've done everything in order to make >encrypt passwd working: > > (1) I converted passwd to smbpasswd > >cat /etc/passwd | mksmbpasswd.sh > smbpasswd > >This resulted in a new smbpasswd file: > >-rw-r--r-- 1 root root 4202 May 21 12:06 smbpasswd > > (2) Here is my /etc/samba/smb.conf file > >[global] > workgroup = MYGROUP > security = USER > log file = /var/log/samba-log.%m > lock dir = /var/lock/samba > encrypt passwords = Yes > smb passwd file = /etc/samba/smbpasswd > > [homes] > comment = Home Directory > read only = No > create mask = 0750 > browseable = No > > [tmp] > comment = Temporary file space > path = /tmp > read only = No > >Note that the smb.conf file worked in the >PlainTextPasswd mode before the two parameters >were added: > > encrypt passwords = Yes > smb passwd file = /etc/samba/smbpasswd > > (3) I restarted Samba daemon > > /etc/init.d/smb restart > > (4) I followed the test steps as outlined in >diagnosis.txt by Andrew Tridgell > >But every attempt to connect to the smb server got >denied: > >[root@star samba]# smbclient -L star >added interface ip=192.168.1.1 bcast=192.168.1.255 >nmask=255.255.255.0 >Password: >session setup failed: ERRSRV - ERRbadpw (Bad password >- name/password pair in a >Tree Connect or Session Setup are invalid.) >[root@star samba]# > > The following transcript may also be of help in >finding what's wrong. > >[root@star samba]# smbclient -L star -N >added interface ip=192.168.1.1 bcast=192.168.1.255 >nmask=255.255.255.0 >Anonymous login successful >Domain=[MYGROUP] OS=[Unix] Server=[Samba 2.2.1a] > >Sharename Type Comment > - --- > tmpDisk Temporary file space > IPC$ IPC IPC Service (Samba >2.2.1a) > ADMIN$ Disk IPC Service (Samba 2.2.1a) > > Server Comment > ---- > STAR Samba 2.2.1a > > WorkgroupMaster > ---- > MYGROUP STAR >[root@star samba]# > > >I suspect my Samba binary doesn't acctually support >encrypt passwd, but how can I tell if it is or not? > >Thanks in advance. > >Chimin Yen > > > > > > > > > > > > > > > >__ >Do You Yahoo!? >LAUNCH - Your Yahoo! Music Experience >http://launch.yahoo.com > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba as PDC with w2k clients
Dear plugbert, try using this command smbpasswd -a -m machine1$ Double check that the machine name has a $ at the end of it in /etc/passwd. -Sam At 06:19 AM 5/21/2002 -0700, plug bert wrote: >Hello! > >A good day to you all. i'm trying to set up >samba(2.2.3a, right out of the rh7.3 cds) as a PDC. >i've already read through the Samba-howto collection, >and am confident that i've put in all the necessary >samba options. > >/etc/samba/smb.conf: > >[global] >netbios name = pdc1 >workgroup = testing >security = user >domain logon = yes >domain master = yes >local master = yes >domain admin group=@admins >encrypt passwords = yes >smb passwd file = /etc/samba/smbpasswd >unix password sync = yes >pam password change = yes >logon script = logon.bat > >[netlogon] >path = /home/netlogon >writable = no >write list = @admins > > i have also created the necessary machine and user >accounts in /etc/passwd and /etc/samba/smbpasswd: > >useradd machine1$ >smbpasswd -a -m machine1 > > >However, i keep getting this error in log.smbd >whenever i try to add my 2k pro client: > >rpc_server/src_samr.c: api_samr_set_userinfo(670) >api_samr_set_userinfo: Unable to unmarshall >SAMR_Q_SET_USERINFO > >passdb/pdb_smbpasswd.c: pdb_getsampwrid(1416) >unable to open passdb database > >Any suggestions as to the cause of the problem? >Thanks in advance. > > > > > > > >__ >Do You Yahoo!? >LAUNCH - Your Yahoo! Music Experience >http://launch.yahoo.com > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Windows 2000 and Samba
It sounds like you're having a windows networking error - do you have both faulty w2k machines and the samba server pointing at the WINS server? Or better yet, is your samba server configured as a WINS server? If it's a windows networking error, try renaming %system root%\system32\drivers\etc\lmhosts.sam to %system root%\system32\drivers\etc\lmhosts (i.e. remove the .sam file suffix) read the comments in the lmhosts file and edit the lmhosts file as appropriate for your network Finally, check your DNS setup on the two faulty w2k machines, w2k relies on DNS a lot more for netbios name resolution. From the w2k command prompt, do a nslookup server name and see how long that takes - if that's not working you may need to tweak your DNS settings on those two w2k machines. I'm curious as to what's going on, so keep us posted. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison At 12:18 PM 5/9/2002 -0600, Paul Harlow wrote: >"Windows cannot find '\\server1'. Check Spelling..." >and >"The semaphore timeout has expired..." >The semaphore error comes up about a tenth of the time that the other one >does. > >This server can be resolved without problems using both WINS and DNS. We're >not reaching across a subnet here, all machines affected are on the same >subnet. All machines, Win2k and WinNT4 can see this server in Network >Neighborhood/Places fine as well. It's just that when you click on them or >type their names in the address field they're not accessible with the given >messages returned as errors. >If already tried removing and reinstalling Windows Networking from these >machines to no avail. > >Paul > >-Original Message- >From: Sam Barasch [mailto:[EMAIL PROTECTED]] >Sent: Thursday, May 09, 2002 11:45 AM >To: Paul Harlow; Samba List (E-mail) >Subject: Re: [Samba] Windows 2000 and Samba > > >Can the w2k pro machines see the AIX box in my network places? > >are you trying to do this across subnets? > >Is there an error message you can share? > >At 11:04 AM 5/9/2002 -0600, Paul Harlow wrote: > >I have a Samba server running on an AIX 4.4.3 RS6000 that has been serving > >up files without problem. Recently, a pair of machines, both Windows 2000 > >Pro, haven't been able to gain access to any of the Samba resources on the > >AIX server though they were both able to previously. Other WinNT and Win2k > >machines can get to these shared resources fine, just not these two. > >I haven't found anything yet to give a reason why or support a fix for >this. > >Does anyone have any suggestions or paths to lead me down? > > > >Paul Harlow CCNA, MCP > >System and Network Administrator > >SKLD Information Services LLC > >720 S. Colorado Blvd. Suite 1000N > >Denver, CO 80246 > >(303) 820-0861 > >(720) 313-6125 cell > >[EMAIL PROTECTED] > > > > > >-- > >To unsubscribe from this list go to the following URL and read the > >instructions: http://lists.samba.org/mailman/listinfo/samba > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows 2000 and Samba
Can the w2k pro machines see the AIX box in my network places? are you trying to do this across subnets? Is there an error message you can share? At 11:04 AM 5/9/2002 -0600, Paul Harlow wrote: >I have a Samba server running on an AIX 4.4.3 RS6000 that has been serving >up files without problem. Recently, a pair of machines, both Windows 2000 >Pro, haven't been able to gain access to any of the Samba resources on the >AIX server though they were both able to previously. Other WinNT and Win2k >machines can get to these shared resources fine, just not these two. >I haven't found anything yet to give a reason why or support a fix for this. >Does anyone have any suggestions or paths to lead me down? > >Paul Harlow CCNA, MCP >System and Network Administrator >SKLD Information Services LLC >720 S. Colorado Blvd. Suite 1000N >Denver, CO 80246 >(303) 820-0861 >(720) 313-6125 cell >[EMAIL PROTECTED] > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
