RE: Help! IBM xSeries 360
That would be the Woody 3.0r0 running the 2.2.20 kernel. Sorry, I should have mentioned that. As it worked out I was able to get the installation to work using the floppy disks under /dists/woody/main/disks-i386/3.0.23-2002-05-21 on the debian-30r0-i386-binary-1_NONUS.iso image. I installed the kernel and drivers from those disks and did not use the default CD-ROM kernel. It may have worked I just didn't want to try it. I need to hack a new kernel anyway to pick up the second processor on the system which may be an equally fun exercise. Anyway thanks for the input, Brian -Original Message- From: James Troup [mailto:james;nocrew.org] Sent: Friday, November 08, 2002 12:19 PM To: Kimsey-Hickman, Brian Cc: '[EMAIL PROTECTED]' Subject: Re: Help! IBM xSeries 360 Kimsey-Hickman, Brian [EMAIL PROTECTED] writes: I am trying to get Debian on a new IBM xSeries 360 with an Adaptec 7892 adapter and Utra 160 SCSI hard drives. Debian with the normal CD install can't see the drives. I was thinking about using the drivers from the floppies but I could not find anything saying if those drivers are there. Has anyone installed Debian on one of these IBMs that could help? Err, which version of Debian? I've installed Woody onto several x220 and x330's both of which have Adaptec 7892s, e.g. james@hesiod:~$ lspci | grep Adaptec 01:03.0 SCSI storage controller: Adaptec 7892P (rev 02) james@hesiod:~$ -- James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Samba share cannot cross segment
I have two Samba servers configure similarly. One shares fine across our
entire network and the other only works within it's own segment. I have
poured over the smb.conf files and cannot see what it preventing the one
from crossing segments.
I can ping the WINS servers from the bad Samba server. I have two NT 4.0
WINS servers that have a PUSH / PULL relationship set up. I have checked
the database on the WINS server that is on the segment that cannot see the
shares from the bad server. It has an entry with the correct IP for the bad
server. I can see the bad server in the browser list from the segment but
when I click on a share I get:
\\Device is not accessible
The network path was not found
I can also see the good server but I can open it's shares.
These both are Debian 2.2 boxes and I am just
modifying the default smb.conf files. I am hoping a fresh pair of eyes will
help. Any help would be greatly appreciated.
Thanks,
Brian
Good Server with shares that cross the segment:
;
; /etc/smb.conf
;
; Sample configuration file for the Samba suite for Debian GNU/Linux
;
; Please see the manual page for smb.conf for detailed description of
; every parameter.
;
[global]
printing = bsd
printcap name = /etc/printcap
load printers = yes
guest account = nobody
invalid users = root
; security = user is always a good idea. This will require a Unix account
; in this server for every user accessing the server.
; security = user
security = domain
password server = compt-401p
; Change this for the workgroup your Samba server will part of
workgroup = COMPTROLLER
server string = Debian GNU/Linux
; server string = %h server (Samba %v)
; If you want Samba to log though syslog only then set the following
; parameter to 'yes'. Please note that logging through syslog in
; Samba is still experimental.
syslog only = no
; We want Samba to log a minimum amount of information to syslog. Everything
; should go to /var/log/{smb,nmb} instead. If you want to log through
; syslog you should set the following parameter to something higher.
syslog = 0;
; This socket options really speed up Samba under Linux, according to my
; own tests.
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
SO_RCVBUF=4096
; Passwords are encrypted by default. This way the latest Windows 95 and NT
; clients can connect to the Samba server with no problems.
encrypt passwords = yes
; It's always a good idea to use a WINS server. If you want this server
; to be the WINS server for your network change the following
; parameter
; to yes. Otherwise leave it as no and specify your WINS server
; below (note: only one Samba server can be the WINS server).
; Read BROWSING.txt for more details.
wins support = no
; If this server is not the WINS server then specify who is it and uncomment
; next line.
wins server = 172.30.4.8
; Please read BROWSING.txt and set the next four parameters according
; to your network setup. There is no valid default so they are
; commented
; out.
; os level = 0
; domain master = no
; local master = no
; preferred master = no
; What naming service and in what order should we use to resolve host names
; to IP addresses
name resolve order = lmhosts host wins bcast
; This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
; Name mangling options
preserve case = yes
short preserve case = yes
; This boolean parameter controlls whether Samba attempts to sync. the Unix
; password with the SMB password when the encrypted SMB password in
; the
; /etc/samba/smbpasswd file is changed.
unix password sync = false
; For Unix password sync. to work on a Debian GNU/Linux system, the
; following
; parameters must be set (thanks to Augustin Luton
; [EMAIL PROTECTED] for sending the correct chat script for
; the passwd program in Debian Potato).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
; *Retype\snew\sUNIX\spassword:* %n\n .
; The following parameter is useful only if you have the linpopup package
; installed. The samba maintainer and the linpopup maintainer are
; working to ease installation and configuration of linpopup and
; samba.
; message command = /bin/sh -c '/usr/bin/linpopup %f %m %s; rm %s'
; The default maximum log file size is 5 MBytes. That's too big so this
; next parameter sets it to 1 MByte. Currently, Samba rotates log
; files (/var/log/{smb,nmb} in Debian) when these files reach 1000
; KBytes.
; A better solution would be to have Samba rotate the log file upon
; reception of a signal, but for now on, we have to live with this.
max log size = 1000
[homes]
comment = Home Directories
browseable = no
; By default, the home directories are exported read only.
How do you set time limits in ProFTP using PAM?
I am trying to set time limits on when users can use our ProFTP site using PAM. I am using Potato 2.2 Rev 2. I opened /etc/pam.d/ftp and added the line: account required pam_time.so Then I opened /etc/security/time.conf and added the line ftp;tty* ttyp*;username;Al-0500 Looking at the documentation that's all I saw that you should have to do but obviously not because its not working. Does anybody have any ideas? Thanks, Brian
RE: Dual NIC Problem
Sorry I have taken so long as well. I got pulled onto another project. Yes, I have both configurations in /etc/network/interfaces. The only difference is that eth1 is on a different segment so the only number that is similar between the two NIC is the subnet mask. This is what I have (number are fictisous): iface eth0 inet static address 172.30.14.171 network 172.30.14.0 netmask 255.255.254.0 broadcast 172.30.15.255 gateway 172.30.14.2 iface eth1 inet static address 172.30.12.219 network 172.30.12.0 netmask 255.255.254.0 broadcast 172.30.13.255 gateway 172.30.12.2 Now, I am using 3Com 3C905B NICs. I think I am going to swap them out for some Intel Pro/100s and see what happens. Thanks, Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christen Welch Sent: Thursday, October 05, 2000 6:02 AM To: 'debian-user@lists.debian.org' Subject: Re: Dual NIC Problem Sorry for the tardiness of my reply... Let me just give a run down of some stuff: /etc/network/interfaces: - iface lo inet loopback iface eth0 inet static address 172.16.12.42 network 172.16.12.0 netmask 255.255.255.0 broadcast 172.16.12.255 gateway 172.16.12.1 - and you have the same type info for eth1 in there too /etc/init.d/network shouldn't have anything in it If everything looks ok here, and /etc/hosts.deny and /etc/hosts.allow are set up properly, I'm really out of ideas. Sorry about that. If I can think of something else, I'll be sure to post it. -- Chaotic42 [EMAIL PROTECTED] http://www.pobox.com/~chaotic42/ http://www.bigplasticfork.org/ We are what we repeatedly do - Aristotle
RE: X-windows + Rage Fury Pro Vivo compatibility
Yes, I have. However, I used x86config to set up my configuration file not x86setup. Brian -Original Message- From: ValentÃn Alba [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2000 4:46 PM To: debian-user@lists.debian.org Subject: X-windows + Rage Fury Pro Vivo compatibility Does anybody make X-windows run with ATI Rage 128 Pro with Debian 2.2? Even in VGA or SVGA mode? Thanks -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
What happened to SSH?
What has happened to SSH? I cannot find in dselect and I have tried pointing apt to us.debian.org, ca.debian.org and midco. It is just not there. I did look at the bugs page and there are two grave level bugs so maybe it was removed temporarily because of that but I don't know for sure. I'm sure someone knows. Also, if I cannot use SSH is there a suitable alternative? Thanks, Brian
RE: Dual NIC Problem
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christen Welch Sent: Saturday, September 30, 2000 1:52 AM To: 'debian-user@lists.debian.org' Subject: Re: Dual NIC Problem On Fri, Sep 29, 2000 at 09:05:30AM -0400, Kimsey-Hickman, Brian [EMAIL PROTECTED] wrote: Well it sure didn't take to long to reach the limit of my knowledge. Heh, this is my first real crack at helping anyone, so I know how you feel. I hope I can help you solve this. If not, feel free to call me at all hours of the night to chew me out :) Heck, I'm just happy to have someone to bounce ideas off of. You won't get any crankiness from me. I could not find anything that had the a telnet 127.0.0.1 110 line. Sorry, I am a new user. Sorry, I meant just run that at the prompt. That should take you into your own mail server, should you have one running. The point of this being, if you have telnetd running, and can't telnet in to the default port, maybe you could telnet into another port. Okay, I tried that and got an error Unable to connect to remote host: Connection Refused When I built this machine I did not use any of the simple installation setups like for a Server, Workstation or Scientific Workstation. I selected advanced and all I selected was telnet, ifconfig and tcpdump. So, unless mail services are selected and installed by default this machines probably would not have them. Basically, all I want this machine to do is to monitor a network segment while I telnet into from another segment to take a look. I could go ahead and install mail services for diagnostic purposes I don't have a problem with that. now. Both are purely experimental at this point. I did check the hosts file at it does have the machine name and IP number. When I said I could ping I meant I can the IP address not the device name. Here's where my understanding of the whole network stuff fades away :) Are you trying to ping /dev/eth0? Can you give me the output of netstat -rn on all of the systems? The dual NIC machine Destination Gateway Genmask Flags Mss Window irtt Iface 172.30.4.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 172.30.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 172.30.6.2 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 172.30.4.2 0.0.0.0 UG 0 0 0 etho The machine I am trying to telnet from Destination Gateway Genmask Flags Mss Window irtt Iface 172.30.4.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 0.0.0.0 172.30.4.2 0.0.0.0 UG 0 0 0 etho -- Chaotic42 [EMAIL PROTECTED] http://www.pobox.com/~chaotic42/ http://www.bigplasticfork.org/ Think for yourself and let others enjoy the privilege of doing so too - Voltaire
RE: Dual NIC Problem
Thanks, for the advice. However I did notice that I do not have /etc/init.d/networks file. I have a /etc/init.d/networking file. I noticed this when I first started looking but thought that the file names might have been changed between Debian 2.1 and 2.2. Do you know, or anyone for that matter, if that is the case? Or do I have a botched installation? Thanks, Brian -Original Message- From: Krafthefer, Kevin [mailto:[EMAIL PROTECTED] Sent: Friday, September 29, 2000 11:59 AM To: '[EMAIL PROTECTED]' Subject: Re: Dual NIC Problem Brian, I've grappled with multiple nics a few times, most of the time successfully but not always. Without being able to pin-point your problem from here, I offer this advice: potentially useful commands: o netstat o ifconfig potentially useful files: o /etc/init.d/networks (basically, this is where your network configuration is set): o /etc/networks o /etc/inet.d potentially useful books: o Linux Network Administrators Guide, second edition is out (O'Reilly) potentially useful words: o stick to ip addresses until you get you basic network functionality working, then add a name server on a debian box (not NT, microsoft's implementation of dns is limited and a bit unstable [go figure]); get O'Reilly's dns/bind book for name server configuration o you can bind multiple ip addresses to one nic, this can eliminate possibilities of hardware conflicts between the nics but exposes you to security issues Good luck and stick with it. It will eventually work. Krafty
RE: Dual NIC Problem
Well it sure didn't take to long to reach the limit of my knowledge. I really don't know where to look to find what services are running. I found a /etc/services file but that looked more like porting information (telnet 23/tcp). I could not find anything that had the a telnet 127.0.0.1 110 line. Sorry, I am a new user. I am trying this as work and we are on an ethernet network running TCP/IP on class b numbers. There are only two Debian machines on the network right now. Both are purely experimental at this point. I did check the hosts file at it does have the machine name and IP number. When I said I could ping I meant I can the IP address not the device name. I don't have anything set up for name resolution right now for these machines. We are basically an NT VAX shop. The second experimental machine that has only one NIC card I can telnet into just fine without any problems. In setting up the second NIC card on the first machine I could not find much documentation so I just decided to edit the /etc/host file and added another line with the same device name and a second IP address on another segment. Then I went to the /etc/network/interfaces file and added a iface eth1 inet static section defining the IP address, netmask, network, broadcast and gateway numbers. That all I did. I could not find much more information in the How Tos, online documentation or SAMs Debian Unleashed book. I am sure I have missed something. In any case thanks for the help and I hope I have provided enough information to fuel an answer. Brian On Thu, Sep 28, 2000 at 03:31:38PM -0400, Kimsey-Hickman, Brian [EMAIL PROTECTED] wrote: I have tried to set up a telnet session using both the ip and host name. When using the ip number I get just the telnet prompt with no error messages. Do you have any services running that you could telnet into? For example: telnet 127.0.0.1 110 or something like that to see if anything is running. When I use the host name and get and Unknown Host error. I can ping the ip address without any problem. Sounds like a name configuration error. How is your network set up? Are you trying to access a home network from work? -- Chaotic42 [EMAIL PROTECTED] http://www.pobox.com/~chaotic42/ http://www.bigplasticfork.org/ We are what we repeatedly do - Aristotle
Dual NIC Problem
I am a new Debian (2.2) user and am trying to set up an Intel machine for two NIC cards. One NIC will monitor (tcpdump) one ethernet segment while I telnet into the machine on the other NIC on another segment. eth0 is on the segment I want to monitor. eth1 is the one I was planning to telnet into. The problem is that I do not get a login prompt when I telnet into the device, I get a telnet prompt. If someone could point me in the right direction, either to some written resources or advice, I would greatly appreciate it. Thanks, Brian
RE: Dual NIC Problem
Thanks for the response. I have tried to set up a telnet session using both the ip and host name. When using the ip number I get just the telnet prompt with no error messages. When I use the host name and get and Unknown Host error. I can ping the ip address without any problem. Brian On Thu, Sep 28, 2000 at 11:38:13AM -0400, Kimsey-Hickman, Brian wrote: I am a new Debian (2.2) user and am trying to set up an Intel machine for two NIC cards. One NIC will monitor (tcpdump) one ethernet segment while I telnet into the machine on the other NIC on another segment. eth0 is on the segment I want to monitor. eth1 is the one I was planning to telnet into. The problem is that I do not get a login prompt when I telnet into the device, I get a telnet prompt. If someone could point me in the right direction, either to some written resources or advice, I would greatly appreciate it. Did you try telnet ip_or_name_of_machine? You only get a prompt if you only type in telnet. What error messages do you get? Can you ping your machine's ip-adresses? -- Thomas Guettler Office: [EMAIL PROTECTED] www.interface-business.de Private:[EMAIL PROTECTED] http://yi.org/guettli -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
