toasters

toasters@lists.teaparty.net

1 participants
13515 discussions

Re: Accessing CIFS shares with Unix authentication
by Mark Muhlestein 10 Mar '99

10 Mar '99

>At 01:25 pm 3/10/99 -0500, Will Harper wrote: >>I can't answer your question directly, but I have "heard" that CIFS is a >>problem. It works ok, when it is working, but when it hiccups, it is not >>easily corrected. When a CIFS connection is broken, it stays broken. >> >>A vendor's engineer (Auspex) told me that he had found that an NFS client >>on NT actually provided better end results for all of the H-A storage >>systems that he had worked with. He suggested Samba or Hummingbird. NFS, >>he explained, keeps trying to reconnect until you fix the problem, and then >>NFS fixes itself. Samba? Samba is a CIFS server. As Dave Hitz pointed out, there are tradeoffs with the various protocols, but with a Netapp box you can use whichever suits your needs best. Mark Muhlestein -- mmm(a)netapp.com

1 0

Re: Accessing CIFS shares with Unix authentication
by Jason D. Kelleher 10 Mar '99

10 Mar '99

In message <01BE6AF9.7FE779F0.willh(a)infi.net>, Will Harper writes: >I can't answer your question directly, but I have "heard" that CIFS is a >problem. It works ok, when it is working, but when it hiccups, it is not >easily corrected. When a CIFS connection is broken, it stays broken. > >A vendor's engineer (Auspex) told me that he had found that an NFS client >on NT actually provided better end results for all of the H-A storage >systems that he had worked with. He suggested Samba or Hummingbird. NFS, >he explained, keeps trying to reconnect until you fix the problem, and then >NFS fixes itself. > >Will Harper, MCSE Auspex told us the same... right before they mentioned that CIFS wasn't supported for partitions under ClusterGuard(tm) -- their shared disk failover option. Not that I disagree... I really like the the statelessness (not sure if that's a word) of NFS. Any truth to the legend that NFS kept state, but was changed because the stability of the servers was questionable? jason

1 0

NFS fundamentally broken ???
by Philip Thomas 10 Mar '99

10 Mar '99

Hi, An experienced sys admin and a colleague of mine argue that NFS is "fundamentally broken", in the sense that because of it's stateless architecture, a NFS client can "hang" during shutdown if it's NFS server(s) does not respond. This is aggravated when an "ack" is lost between server/client. He claims to have gone through NFS code while he was at a prestigious university. Granted I am not an expert, all the years I have worked with NFS, I never had a problem shutting down a system because it's NFS mount was not "responding". But I am hoping for folks with "theoretical" background to shed some more light into the above argument. This brings to the second question. The same person emphasize the above issue as an added reason for not having NFS mount points on his HP High Availability (ServiceGuard). Is there any site out there, in this wide world, using HP's ServiceGuard (or any other HA) on a system that is an NFS client and would like to comment on their experience in private or in this forum. Philip Thomas Motorola - PEL, M/S M350 2200 W. Broadway M350 Mesa, AZ 85202 rxjs80(a)email.sps.mot.com (602) 655-3678 (602) 655-2285 (fax)

1 0

RE: Accessing CIFS shares with Unix authentication
by Sam Schorr 10 Mar '99

10 Mar '99

Will, It is not true that CIFS connections "stay broken" as you state. We are exclusively a CIFS environment and we have frequent CIFS disconnects. There are a number of reasons for this, and it is true that CIFS behaves very differently then NFS. However, I think Auspex has a lot to prove when it makes the NFS claim of better "results" whatever, that means. A CIFS client will reconnect automatically to the CIFS share as long as that share remains available to the NT domain. -----Original Message----- From: Will Harper [mailto:willh@infi.net] Sent: Wednesday, March 10, 1999 10:26 AM To: 'P.S.Jones'; toasters(a)mathworks.com Subject: RE: Accessing CIFS shares with Unix authentication I can't answer your question directly, but I have "heard" that CIFS is a problem. It works ok, when it is working, but when it hiccups, it is not easily corrected. When a CIFS connection is broken, it stays broken. A vendor's engineer (Auspex) told me that he had found that an NFS client on NT actually provided better end results for all of the H-A storage systems that he had worked with. He suggested Samba or Hummingbird. NFS, he explained, keeps trying to reconnect until you fix the problem, and then NFS fixes itself. Will Harper, MCSE -----Original Message----- From: P.S.Jones [SMTP:P.S.Jones@durham.ac.uk] Sent: Wednesday, March 10, 1999 11:01 AM To: toasters(a)mathworks.com Subject: Accessing CIFS shares with Unix authentication We have a Network Appliance 740 Filer for evaluation and want to try it in a mixed Unix and NT environment. I think we can handle the Unix side without any real problems. What we are struggling with is how to provide access to the CIFS file store to our NT clients by supplying Unix credentials? I'll explain this in a bit more detail. Our NT service has no user accounts, or rather it has one, a general auto logon account. Within this account's logon script we prompt for authentication details (real user ID and password) and then map network shares against our existing Netware 3.1 servers. In the summer we plan to retire Netware 3.1 and provide the home file store from a Unix like system. We've tried Samba and quite like it but we want to evaluate the Filer as well. But how can we map a CIFS share from the Filer using just Unix credentials? I'm trying to read the documentation at the moment and have come across the usermap.cfg file mechanism, but this doesn't seem quite appropriate since we don't have any NT accounts. I wonder if anyone on this list has solved a problem like this? Are we going to have to run Samba anyway for the authentication? Any comments gratefully received. -- Paul Jones, ITS, University of Durham, South Road, Durham DH1 3LE Email: P.S.Jones(a)durham.ac.uk Phone/Fax: 0191 374 2879/3741

1 0

CIFS Setup Problems
by Alexander Strauss 10 Mar '99

10 Mar '99

Hello, I tried to setup CIFS on my NetApp Fileserver using NT Domain authentication. The Filer has been added to the Domain by the NT server manager and can find the primary domain controller through the WINS service. Then I get the following error message: > filer> cifs setup > [ ... ] > Will this filer use an NT Domain for authentication? [yes]: > Enter the NT Domain for the filer: EUROPE1 > > CIFS local server is registering... > CIFS server is beginning domain installation. > CIFS server is locating PDC. > CIFS - Primary Domain Controller must be active for installation. > > CIFS local server is shutting down... But the primary domain controller *is* definitely active. Any suggestions? thank you, -- Alexander Strauss - Email: strauss(a)ti.com - TI-MSG: ALST System Administrator - Mixed Signal & Logic Products Europe Texas Instruments Deutschland GmbH, 85350 Freising, Germany Phone: +49 8161 80-3606 - Fax: +49 8161 80-4477

4 3

Re: Accessing CIFS shares with Unix authentication
by Mark Muhlestein 10 Mar '99

10 Mar '99

You can use /etc/passwd accounts. When you run 'cifs setup' say that you don't want to install into a domain. Then you'll have to set up NIS or copy in /etc/passwd to the filer. If you are using NT 4 service pack 3 or higher clients you will also have to change a registry setting to allow plaintext passwords. That's described by Microsoft (from their knowledge base web site): "Unable to connect to SMB server with unencrypted password due to redirector. Cause: After applying Service Pack 3, the SMB redirector does not send unencrypted passwords until a registry entry is added to enable unencrypted passwords. Solution: Configure the SMB server to use encrypted passwords, or edit the registry of the Windows NT computers to enable sending unencrypted passwords. NOTE: Configuring the SMB server to use encrypted passwords is the preferred solution, since the registry on each client machine must be edited. NOTE: The following procedure describes how to edit the registry to enable sending unencrypted passwords. This procedure must be performed on each client machine which connects to the SMB server. CAUTION: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Read the following procedure carefully before proceeding. 1) Run the program REGEDT32. 2) Navigate to the following key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rdr\Parameters 3) Add the value entry 'EnablePlainTextPassword' of data type REG_DWORD, and set the value to 1. NOTE: The registry entry 'EnablePlainTextPassword' has a range of values from 0 (plaintext password disabled) to 1 (plaintext password enabled). 4) Restart the computer to enable the new settings. -----Original Message----- From: P.S.Jones <P.S.Jones(a)durham.ac.uk> To: toasters(a)mathworks.com <toasters(a)mathworks.com> Date: Wednesday, March 10, 1999 8:08 AM Subject: Accessing CIFS shares with Unix authentication >We have a Network Appliance 740 Filer for evaluation and want to try >it in a mixed Unix and NT environment. I think we can handle the Unix >side without any real problems. What we are struggling with is how to >provide access to the CIFS file store to our NT clients by supplying >Unix credentials? I'll explain this in a bit more detail. > >Our NT service has no user accounts, or rather it has one, a general >auto logon account. Within this account's logon script we prompt for >authentication details (real user ID and password) and then map >network shares against our existing Netware 3.1 servers. In the summer >we plan to retire Netware 3.1 and provide the home file store from a >Unix like system. We've tried Samba and quite like it but we want to >evaluate the Filer as well. But how can we map a CIFS share from the >Filer using just Unix credentials? > >I'm trying to read the documentation at the moment and have come >across the usermap.cfg file mechanism, but this doesn't seem quite >appropriate since we don't have any NT accounts. I wonder if anyone >on this list has solved a problem like this? Are we going to have to >run Samba anyway for the authentication? > >Any comments gratefully received. > >-- >Paul Jones, ITS, University of Durham, South Road, Durham DH1 3LE >Email: P.S.Jones(a)durham.ac.uk Phone/Fax: 0191 374 2879/3741 >

2 1

RE: CIFS Setup Problems
by Mike Ball 10 Mar '99

10 Mar '99

Alexander, Make sure you add the filer via Server Manager on you NT Domain before running cifs setup. The filer must be added to the domain before running cifs setup. If this has been done, see if you can ping the PDC ip from your filer console! If your not able to ping the PDC, you may be dealing with a routing issue. Hope this helps, Mike -----Original Message----- From: Alexander Strauss [SMTP:strauss@ti.com] Sent: Wednesday, March 10, 1999 11:30 AM To: toasters(a)mathworks.com Subject: CIFS Setup Problems Hello, I tried to setup CIFS on my NetApp Fileserver using NT Domain authentication. The Filer has been added to the Domain by the NT server manager and can find the primary domain controller through the WINS service. Then I get the following error message: > filer> cifs setup > [ ... ] > Will this filer use an NT Domain for authentication? [yes]: > Enter the NT Domain for the filer: EUROPE1 > > CIFS local server is registering... > CIFS server is beginning domain installation. > CIFS server is locating PDC. > CIFS - Primary Domain Controller must be active for installation. > > CIFS local server is shutting down... But the primary domain controller *is* definitely active. Any suggestions? thank you, -- Alexander Strauss - Email: strauss(a)ti.com - TI-MSG: ALST System Administrator - Mixed Signal & Logic Products Europe Texas Instruments Deutschland GmbH, 85350 Freising, Germany Phone: +49 8161 80-3606 - Fax: +49 8161 80-4477

1 0

RE: CIFS Setup Problems
by Hawley, Rob 10 Mar '99

10 Mar '99

Problems such as this are typically caused by problems with the name service configuration. If you are running 5.1 or later, then you can use the command "cifs testdc" to diagnose problems such as these. Filer>cifs testdc [<wins addr> ] domain name [<optional name to test>] This should give you a printout like this : nttest> cifs testdc 10.10.10.55 nt-domain nttest Test will use WINS name resolution Testing WINS address...10.10.10.55 is alive Testing name registration... succeeded Current Mode of NBT is H Mode Netbios scope "" <-------if you use netbios scope you need to set the scope using the options. Registered names... NTTEST < 0> WINS <-- the filer is registering with WINS. If you used broadcasts, then this would say broadcast. If you tried to register with WINS and this says broadcast -->Watch Out. WINS registration failed Testing Primary Domain Controller found 1 addresses <- In your case I would expect this to fail trying 10.150.13.15...10.150.13.15 is alive <- can you route to the domain controller? found PDC FRENCH40 <- OK something is saying it is domain controller, is it really behaving like a domain controller. Testing all Domain Controllers found 3 addresses trying 10.150.13.15...10.150.13.15 is alive trying 10.150.13.15...10.150.13.15 is alive trying 192.168.2.66...192.168.2.66 is alive found DC FRENCH40 at 10.150.13.15 Not able to communicate with DC 10.150.13.15 found DC NT-DOMAIN-BDC at 192.168.2.66 If your filer is multihomed, you are using WINS, and the registration test fails, then go to the WINS server and ping (or tracert) each interface on the filer. If the WINS server does not have a route to an interface then WINS registration will fail. The printout below does not indicate that this has happened, but others may find this useful. Make sure the domain contains a freshly created machine account for the filer. You can create a machine account using Server manager. Check to make sure that the domain controller is configured with the TCP network stack. We do not implement netbios. Hope this helps. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > mailto: hawleyr(a)netapp.com <mailto:hawleyr@netapp.com> US Mail: Network Appliance Inc. > Phone: 408-367-3254 2770 San Tomas Expressway > FAX: 408-367-3451 Santa Clara, CA 95051 -----Original Message----- From: Alexander Strauss [mailto:strauss@ti.com] Sent: Wednesday, March 10, 1999 8:30 AM To: toasters(a)mathworks.com Subject: CIFS Setup Problems Hello, I tried to setup CIFS on my NetApp Fileserver using NT Domain authentication. The Filer has been added to the Domain by the NT server manager and can find the primary domain controller through the WINS service. Then I get the following error message: > filer> cifs setup > [ ... ] > Will this filer use an NT Domain for authentication? [yes]: > Enter the NT Domain for the filer: EUROPE1 > > CIFS local server is registering... > CIFS server is beginning domain installation. > CIFS server is locating PDC. > CIFS - Primary Domain Controller must be active for installation. > > CIFS local server is shutting down... But the primary domain controller *is* definitely active. Any suggestions? thank you, -- Alexander Strauss - Email: strauss(a)ti.com - TI-MSG: ALST System Administrator - Mixed Signal & Logic Products Europe Texas Instruments Deutschland GmbH, 85350 Freising, Germany Phone: +49 8161 80-3606 - Fax: +49 8161 80-4477

1 0

Accessing CIFS shares with Unix authentication
by P.S.Jones 10 Mar '99

10 Mar '99

We have a Network Appliance 740 Filer for evaluation and want to try it in a mixed Unix and NT environment. I think we can handle the Unix side without any real problems. What we are struggling with is how to provide access to the CIFS file store to our NT clients by supplying Unix credentials? I'll explain this in a bit more detail. Our NT service has no user accounts, or rather it has one, a general auto logon account. Within this account's logon script we prompt for authentication details (real user ID and password) and then map network shares against our existing Netware 3.1 servers. In the summer we plan to retire Netware 3.1 and provide the home file store from a Unix like system. We've tried Samba and quite like it but we want to evaluate the Filer as well. But how can we map a CIFS share from the Filer using just Unix credentials? I'm trying to read the documentation at the moment and have come across the usermap.cfg file mechanism, but this doesn't seem quite appropriate since we don't have any NT accounts. I wonder if anyone on this list has solved a problem like this? Are we going to have to run Samba anyway for the authentication? Any comments gratefully received. -- Paul Jones, ITS, University of Durham, South Road, Durham DH1 3LE Email: P.S.Jones(a)durham.ac.uk Phone/Fax: 0191 374 2879/3741

1 0

test
by Jason Middlebrooks 09 Mar '99

09 Mar '99

test Jason Middlebrooks Systems Engineer Datalink Phone: 888-933-9327x260 2264 Northwest Parkway, Suite I Pager: 888-502-1625 Marietta, GA 30067 Fax: 770-933-9272

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters