toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

netapp meets bugtraq. again.
by fubar＠mathworks.com 01 May '99

01 May '99

Ok, so I don't have the docs handy.. but if you have an "-access" options, it just seems kinda intuitive to me that you might actually *USE IT*. But maybe it's just me. ------- Start of forwarded message (RFC 934 encapsulation) ------- From: pashdown(a)XMISSION.COM (Pete Ashdown) Subject: Network Appliance NFS filer root hole Date: 28 Apr 1999 15:58:45 -0400 Organization: Bugtraq List Message-ID: <199904281658.KAA14944(a)slack.xmission.com> Reply-To: Pete Ashdown <pashdown(a)XMISSION.COM> For Network Appliance NFS filer release: NetApp Release 5.2.1: Thu Dec 31 12:56:45 PST 1998 Following "Example 1" on page 136 of the "System Administrator's Guide" for the Network Appliance results in a gaping hole. In this example, they explain that "the following line exports the root directory of the default filter volume to the administration host with root privileges." /vol/vol0 -root=adminhost This is all fine and good, but it also exports to the WORLD with root privileges. You have to specify either "-access", or "-rw", or "-ro" in addition to "-root" for this not to happen. When I mentioned this to my NetApp SE, I was met with quizzical looks, but no code-update or patch. Thusly, I sent it to bugtraq. ------- End -------

4 6

RE: Digital UNIX clients -- no non-root access
by Muhlestein, Mark 01 May '99

01 May '99

I'm not sure what your problem is, but I can verify that internally here at NetApp we use DU 4.0D (rev 878) extensively on several Alpha machines against multiple filers with no issues. We have also run with 4.0E. What version of the filer software are you running? Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: sirbruce(a)ix.netcom.com [mailto:sirbruce@ix.netcom.com] Sent: Monday, April 26, 1999 6:39 PM To: jgaski(a)WPI.EDU; toasters(a)mathworks.com Subject: Re: Digital UNIX clients -- no non-root access On 04/26/99 21:11:27 you wrote: >I have an open call with Network Appliance, but they have said that >there must be something strange in Compaq's implementation of the NFS >client. The same error occurs on Digital UNIX 4.0D pl3, 4.0E pl1, and >5.0 beta. It occurs whether the mount is soft or hard, udp or tcp, >nfsv3 or nfsv2. > >It seems like such a large, ubiquitous error that I can't believe >noone would have seen it before. I thought that Digital UNIX support >was standard, and I can't imagine how all of our Alpha clients could >be non-standard in such a way. You'd be surprised. Lots of vendors have little quirks in their implementation that, while they happen to work okay with one server, are really out of spec and may not work with another. However, I know that Digital Unix *used* to work, but the last I ever saw personally work was 4.0C. So either they've changed something, or something in the new Netapp release fixed/broke something. Bruce

4 5

Re: Hardware for F330
by Jason D. Kelleher 30 Apr '99

30 Apr '99

In message <3729EEE9.AB4CD895(a)netapp.com>, Jerry Talkington writes: >Jay Orr wrote: >> >> Hi all! >> >> I was wondering if anyone can help. We are a small shop with 2 F330's wit >h >> 2 disk cabinets on each one. We were looking into adding another tray on >> each, but were told by NetApps that they are no longer available. > >I can't comment on the availability, but the F330 only supports two >shelves... Try again. That might be what it "officially" supports now, but we bought ours w/ two shelves and NetApp sold us two more. It's running w/ 4 shelves full of 4GB drives just fine. jason

2 1

Unable to log onto NetApp machine
by michael＠applix.com 30 Apr '99

30 Apr '99

We've got a NetApp machine at our site (F330, NetApp Release 4.3.1: Wed Jan 21 02:57:32 PST 1998) that we can't log in to. It's up and running fine, and we can use rsh to run commands (like version or exportfs), but if I try to telnet to the box all the passwords I try don't work. On the system that's controling that particular server (Digital Unix), the etc directory that's mounted from the filer had no password file in it, and even after copying the passwd file from another NetApp box into the etc directory I'm still unable to get in. Do I need to reboot the filer, or is there some magic I can perform to set the password? There doesn't appear to be a passwd command, and checking the options command doesn't show anything that looks like it might apply.... Thanks in advance, -Mike -- Michael Steeves, System and Network Administrator (msteeves(a)applix.com) "I've got to start listening to those quiet, nagging doubts." -- Calvin and Hobbes

5 6

Re: Hardware for F330
by Jay Orr 30 Apr '99

30 Apr '99

Yes, that helps alot! Any idea on adding another scsi card? On Fri, 30 Apr 1999, Luke Gain wrote: > Jay, > > I have found that standard Kingston 72pin parity memory works fine in > both my 220 and 330. You should be able to string a 3rd shelf > off of the controller on the motherboard. Don't know where to obtain the > Digital Storageworks shelf (Tech Data used to sell them). > Corprate Systems is normally a good source for drives. (www.corpsys.com) > > Hope this helps. > > -Luke > > > > > > Hi all! > > > > I was wondering if anyone can help. We are a small shop with 2 F330's with > > 2 disk cabinets on each one. We were looking into adding another tray on > > each, but were told by NetApps that they are no longer available. > > > > All I'm looking for is to upgrade the memory, add another scsi controller, > > and another tray (is that asking TOO MUCH???). Questions: Can I use off > > the shelf memory (and what kind)? What about SCSI controllers? Where can I > > get disk trays? Could we instead replace the drives with 9G or 18G drives > > (and what model would we use)? > > > > NetApps solution is to spend $60k+ to upgrade, and all we need is another > > 10G - 20G. The current system works fine, isn't overused, and could handle > > the expansion IF WE CAN FIND THE COMPONENTS... > > > > Thanks for the help. By the by, I've been looking for a toaster FAQ, is > > there one? > > > > ----------- > > Fujitsu - Nexion, St. Louis, MO > > Jay Orr (314) 579-6517 > > > > > > ----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517

1 0

Re: netapp meets bugtraq. again.
by Jason D. Kelleher 30 Apr '99

30 Apr '99

In message <Pine.LNX.4.04.9904291507120.12868-100000(a)phaeton.cebaf.gov>, Bry an Hess writes: > >On Thu, 29 Apr 1999 tkaczma(a)gryf.net wrote: >> >> On Wed, 28 Apr 1999, Kendall Libby wrote: >> >> > ------- Start of forwarded message (RFC 934 encapsulation) ------- >> > From: pashdown(a)XMISSION.COM (Pete Ashdown) >> > >> > /vol/vol0 -root=adminhost >> > >> > This is all fine and good, but it also exports to the WORLD with root >> > privileges. >> >> Are you sure it exports to all with root priviledges or does it just >> export to all read/write but as root only to adminhost? > > >It doesn't export root privs to all, but just exporting read/write to all >machines is scary enough. If I am a malicious user, I can find the mount >points easily enough, mount the filesystems, and create user accounts on >my machine to match any uid on the filer. After that, who needs root privs >except for files owner by uid 0? > >--Bryan This is not a "netapp meets bugtraq" issue. It's an "every NFS server configured by someone who doesn't know what he's doing meets bugtraq" issue. Security is dependent on the competence of the administrator. Of course, here in the USA, no one is responsible for their own actions. So we should report Linux, SunOS, Solaris, HP-UX, AIX, Free BSD, NetBSD, etc... to bugtraq right away!!! And we'll all sue too!!! Ooops, got way too sarcastic at the end there... jason

2 1

Re: Unable to log onto NetApp machine
by sirbruce＠ix.netcom.com 30 Apr '99

30 Apr '99

On 04/29/99 15:39:16 you wrote: >Hmm, this is what I thought of at first, but when I tried it in the lab, >it did not work. I did get it to work (sort of) bye doing #rsh filer >rc_toggle_basic; passwd . You should not use rsh to rc_toggle_basic to get at commands that are normally not accessible via rsh. There are reasons why they aren't rsh-able. Bruce

1 0

RE: How to use CIFS if PDC not on same lan?
by Muhlestein, Mark 30 Apr '99

30 Apr '99

NT requires you to see the PDC in certain cases, because the BDCs are basically read-only replicas of the PDC. One of those cases is setting the machine password, which is done when the server (NT or filer) is installed, then once a week (Sunday morning at 2 or so). You will have to make the PDC visible at least temporarily to install the filer. After that, it will keep pestering you because it won't be able to do the periodic machine account password update. This is really an issue with NT networking. You would have the same problem trying to install an NT member server in the same situation. There are probably some reasonable ways around this problem; your situation is not that unusual. The details depend on what you are trying to accomplish. You should probably work with customer support to see what makes most sense. You will also probably want 5.3, since it preferentially connects to domain controllers based on the IP address, which would mean it would always use the local BDC except for changing the passwords. By the way, you'll find that if your Windows clients cannot see the PDC they will not be able to change their login passwords from their workstations for the same reason: they have to be able to contact the PDC to do that. Mark Muhlestein -- mmm(a)netapp.com -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 29, 1999 1:20 PM To: Puneet Anand Cc: toasters(a)mathworks.com Subject: Re: How to use CIFS if PDC not on same lan? The PDC is not IP reachable from the filer. The filer is on a private backbone, serving NFS/CIFS clients off secondary ethernet interfaces. The BDC happens to be one of those clients. And it has 2 interfaces... On Thu, 29 Apr 1999, Puneet Anand wrote: > Is the PDC registering with the same WINS ? Hopefully yes. > We do need PDC for installation.If this is ONTAP 5.1 or later ,you can > run cifs testdc command with the following options to troubleshoot. > > cifs testdc <wins_ip> <domain_name> <filer_name> > > > -Puneet > __________________ > > > Jaye Mathisen wrote: > > > > I have 2 sites. Site B has a BDC for a domain, and the Netapp. > > Site A connected via T1 has the PDC. > > > > When I try to run CIFS setup, it gets to the part about needing to reach > > the PDC and can't find it, so it aborts. > > > > I'm not sure why it can't just do whatever it needs to do with the BDC > > right there (running WINS)... > > > > Perhaps I need to add some key to WINS for the netapp to see it? >

1 0

Procom Netforce
by Kevin W. Brown 30 Apr '99

30 Apr '99

I just got back from ISPCon, where I saw the Procom Netforce filer, and I was wondering if anyone here has experience with this product. Specifically, they have a 100G fault-tolerant version for around $30K. It has two host "controllers", which are basically Pentium II/III machines that load balance and automatically fail over. It has a journaling file system and snapshot backup capability. We are looking to purchase some new network attached (NFS) storage, and this looks like it just might fit the bill. Thganks! -------------------------------------------------------------------------- Kevin W. Brown | 4080 Water Tank Rd. | E-Mail: kevin(a)qis.net Quantum Internet Services | Manchester, MD 21102 | Voice: 410-239-6920 --------------------------------------------------------------------------

1 0

RE: How to use CIFS if PDC not on same lan?
by Sam Schorr 29 Apr '99

29 Apr '99

The fun question is, what if there is no domain controller available due exactly to the configuration Jaye is trying to install - a separate, "back channel" subnet that is not part of the domain. How would the filers use CIFS then? Install as workstation and do authentication with every file request off a local pwd file? -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 29, 1999 1:20 PM To: Puneet Anand Cc: toasters(a)mathworks.com Subject: Re: How to use CIFS if PDC not on same lan? The PDC is not IP reachable from the filer. The filer is on a private backbone, serving NFS/CIFS clients off secondary ethernet interfaces. The BDC happens to be one of those clients. And it has 2 interfaces... On Thu, 29 Apr 1999, Puneet Anand wrote: > Is the PDC registering with the same WINS ? Hopefully yes. > We do need PDC for installation.If this is ONTAP 5.1 or later ,you can > run cifs testdc command with the following options to troubleshoot. > > cifs testdc <wins_ip> <domain_name> <filer_name> > > > -Puneet > __________________ > > > Jaye Mathisen wrote: > > > > I have 2 sites. Site B has a BDC for a domain, and the Netapp. > > Site A connected via T1 has the PDC. > > > > When I try to run CIFS setup, it gets to the part about needing to reach > > the PDC and can't find it, so it aborts. > > > > I'm not sure why it can't just do whatever it needs to do with the BDC > > right there (running WINS)... > > > > Perhaps I need to add some key to WINS for the netapp to see it? >

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