Subject: 1.600: My named dies frequently, why? From: jpe@ee.egr.duke.edu (John P. Eisenmenger) Running on 3.2, named dies frequently on network's primary name server. Try the following: stopsrc -s named # stop running named setenv MALLOCTYPE 3.1 # use 3.1 memory allocation algorithm /etc/named ... # don't use smit to start named You might be able to use startsrc/smit after setting MALLOCTYPE and get the same effect, but I'm not sure. [According to John, the problem is malloc() in the named code. He also suggests using Berkeley's bind, which he has ported and can be ftp'ed from ftp://ftp.egr.duke.edu/archives/bind-4.8.3.tar.gz. -ed] Two ptfs should fix this problem. Get U412332 and U414752. Christophe Wolfhugel reports that bind 4.9 works fine on AIX 3.2 and without MALLOCTYPE=3.1. ------------------------------ Subject: 1.601: How do I trace ethernet packets on an AIX system? From: afx@muc.ibm.de (Andreas Siegert) Do the following: iptrace -i en0 /tmp/ipt The iptrace backgrounds. Find its process id and kill it when you are ready. Then run ipreport -rns /tmp/ipt >/tmp/ipr and look at the output. The current version of Info does not document the r, n and s options but they are quite useful for layering the output. ------------------------------ Subject: 1.602: What is the authorized way of starting automount at boot time? From: curt@ekhadafi.austin.ibm.com (Curt Finch) I put this in my /etc/inittab: automount:2:once:/usr/etc/automount -T -T -T -v >/tmp/au.se 2>&1 I hereby dub it authorized. Jim Salter writes: You can also use the command: 'mkitab "automount:2:once:/usr/etc/..."' to avoid editing the file by hand. ------------------------------ Subject: 1.603: How do I set a tty port for both dial-in and dial-out? Set the mode of the tty to be either 'shared' or 'delayed'. ------------------------------ Subject: 1.604: How to move or copy whole directory trees across a network The following command will move an entire directory tree across a network while preserving permissions, uids and gids. $rsh RemoteHost "cd TargetDir; tar -cBf - ." | tar -xvBf - Explanation: The tar-create is rsh'd to the remote system and is written to stdout (the pipe). The local system is extracting the tar that is being read from stdin (the pipe). From: abeloni Another method is: rcp -rp host1:/dir host2:/dir ------------------------------ Subject: 1.605: How can I send mail to hosts that cannot be pinged? From: jupiter.sun.csd.unb.ca!dedourek (John DeDourek) AIX 3.2 as shipped is configured to only send mail to mail addresses which include a host name. Many organizations use a mail address whose "host name" part is not a host name (technically an MX name). To change the configuration of the AIX mailer, login as root. Then edit the file /etc/sendmail.cf to remove the comment marker ("# ") at the beginning of the line which reads: # OK MX Now rebuild the machine readable form of the configuration with sendmail -bz and finally restart signal sendmail to load the new configuration by one of the following: reboot or stopsrc -s sendmail startsrc -s sendmail or kill -1 `cat /etc/sendmail.pid` From bofh@mail.teleweb.pt Mon Apr 10 07:56:15 2000 From: bofh@mail.teleweb.pt Newsgroups: comp.unix.aix,comp.answers,news.answers Subject: comp.unix.aix Frequently Asked Questions (Part 3 of 5) Supersedes: Followup-To: comp.unix.aix Date: 7 Apr 2000 19:00:12 +0200 Organization: What ? Lines: 1842 Approved: news-answers-request@mit.edu Distribution: world Expires: 12 May 2000 18:42:27 Message-ID: References: Reply-To: bofh@mail.teleweb.pt (Jose Pina Coelho) NNTP-Posting-Host: p140a23.teleweb.pt X-Trace: srvlis16.teleweb.pt 955123708 25054 212.16.140.23 (7 Apr 2000 16:08:28 GMT) X-Complaints-To: abuse@teleweb.pt NNTP-Posting-Date: 7 Apr 2000 16:08:28 GMT Summary: This posting contains AIX Frequently Asked Questions and their answers. AIX is IBM's version of Unix. Keywords: AIX RS/6000 questions answers Path: lendl.cc.emory.edu!finch!andromeda.5sc.net!news-out.cwix.com!newsfeed.cwix.com!triton.skycache.com!nntp-out.teleweb.pt!news.teleweb.pt!not-for-mail Xref: lendl.cc.emory.edu comp.unix.aix:189305 comp.answers:40080 news.answers:179802 Posted-By: auto-faq 3.3 (Perl 5.005) Archive-name: aix-faq/part3 Revision: 1.10 2000/01/09 21:34:43 Posting-Frequency: monthly ------------------------------ Subject: 1.606: How to configure dialup SLIP IBM's WWW page can lead you to a helpful document From: marvin@tornado.oche.de (Christian Bode) If you don't have problems with slattach you should have PTF bos.obj 3.2.0.0.U411505 installed. I assume that you did the right ifconfig commands to setup your slip-device (for example sl0). 1. Create a group called slip. 2. Create a user slip with smit like this: [Entry Fields] * User NAME [slip] ADMINISTRATIVE User? true User ID [] LOGIN user? true PRIMARY group [slip] Group SET [slip] ADMINISTRATIVE groups [system] SU groups [slip] HOME directory [/home/slip] Initial PROGRAM [/bin/sh] User INFORMATION [SLIP-Dialup] Another user can SU to user? false User can RLOGIN? true TRUSTED PATH? nosak Valid TTYs [/dev/tty1] AUDIT classes [] PRIMARY authentication method [SYSTEM] SECONDARY authentication method [NONE] Max FILE size [2097151] Max CPU time [-1] Max DATA segment [262144] Max STACK size [65536] Max CORE file size [2048] Max physical MEMORY [65536] File creation UMASK [022] EXPIRATION date (MMDDhhmmyy) [0] 3. Create a tty with getty on it: Add a TTY [Entry Fields] TTY type tty TTY interface rs232 Description Asynchronous Terminal Parent adapter sa0 * PORT number [s1] BAUD rate [38400] PARITY [none] BITS per character [8] Number of STOP BITS [1] TERMINAL type [dumb] STATE to be configured at boot time [available] DMA on Read Trigger 0,1,2,3 Transmit buffer count [16] Name of initial program to run [/etc/getty] Note: The following attributes are only applicable if /etc/getty is specified as the initial program to run. Enable program? respawn Run level 2 Enable LOGIN share TIME before advancing to next port setting [0] STTY attributes for RUN TIME [hupcl,cread,brkint> STTY attributes for LOGIN [hupcl,cread,echoe,> RUN shell activity manager no Optional LOGGER name [] 4. Change the hardware characteristics so that it uses NO XON/XOFF handshake section 1.613 also talks about tty flow control. 5. A (new) .profile template for slip accounts is provided in section 8.07. The author, David Migliavacca, writes, "I would also like to assert that, to my experience, it is NOT required that the SLIP user be made "administrative" or member of "system" as other parts of the FAQ (and the original script) say. At least on my machine 8-). I now create SLIP users as members of group slip, it being the ONLY group; allowed ttys are set to the available modem lines only; their home directory is owned by root and the .profile is only readable by group slip. Here's another scenario: From: oosten@angelo.ee.ualberta.ca (Brian Oostenbrink) Operating System: IBM AIX 3.2.1 and 3.2.3 Configuring two RS6000s via a Serial Line Interface Protocol (SLIP) connection over two US Robotics Sportster 14,400 modems. The AIX implementation of SLIP is slightly different from most others. The ifconfig command is used to bring up a serial interface, and the slattach command is used to connect the interface to the serial port used for the connection. Dialer device commands can also be issued when invoking the slattach command, using UUCP chat syntax. The following describes a connection between two machines: local.j.k.l ethernet IP address 129.128.127.21 slip interface IP address 129.1.2.1 remote.a.b.c ethernet IP address 129.11.22.44 slip interface address 129.11.22.1 1. Interface configuration Each machine must have a separate IP address dedicated to the SLIP interface. On remote.j.k.l, start the SLIP interface with: ifconfig sl0 129.11.22.1 129.128.127.1 up and on local.a.b.c: ifconfig sl0 129.128.127.1 129.11.22.1 up It is important in later versions of AIX 3.2.3+ to use the same SLIP interface # as the ptty port #, ie. if you use tty12, use ifconfig sl12 instead of sl0. At this point the interfaces are ready to be connected. 2. tty configuration The tty ports on both machines were configured in an identical manner using smit. [Entry Fields] TTY type tty TTY interface rs232 Description Asynchronous Terminal Parent adapter sa0 PORT number [] + BAUD rate [38400] + PARITY [none] + BITS per character [8] + Number of STOP BITS [1] + TERMINAL type [dumb] STATE to be configured at boot time [available] + DMA on + Read Trigger 0,1,2,3 Transmit buffer count [16] # Name of initial program to run [etc/getty] Note: The following attributes are only applicable if /etc/getty is specified as the initial program to run. Enable program? respawn Run level 2 Enable LOGIN disable + TIME before advancing to next port setting [0] +# STTY attributes for RUN TIME [hupcl,cread,brkint,icr> STTY attributes for LOGIN [hupcl,cread,echoe,cs8,> RUN shell activity manager no + Optional LOGGER name [] On older versions of AIX, we encountered some problems disabling getty, and resorted to changing the /etc/inittab file directly. For example, change tty0:2:respawn:/etc/getty /dev/tty0 to tty0:2:off:/etc/getty /dev/tty0 This will disable getty from running. After creating the SLIP tty device, you will need to change its hardware configuration to disable Xon/Xoff flow control. Software flow control should not be used for SLIP. Type 'smit chtty', and then select sub item 2: Hardware settings. Most of the parameters in the tty configuration are the defaults. 3. Modem Configuration The modems were configured as follows: RTS/CTS flow control enabled. Xon/Xoff software flow control disabled. Usually this is automatic if RTS/CTS is enabled. Data rate, terminal to modem = fixed. This is the baud rate from the tty port to the modem. We used a fixed modem-port transfer rate, set to the fastest speed supported by both the tty port and the modem. Newer modems can use a higher transfer rate between the modem and serial port than the modem to modem rate, which is necessary to use data compression effectively. In our setup, we used 14.4 kBaud modems with a port speed of 38.4 kBaud. If your modem supports this feature, use it, otherwise set the port speed equal to the modem connection rate. On the USR Sportster at&b1 fixes the serial port rate to that of the last AT command. The speed parameter of the slattach command can be used to ensure that this rate is that set in the tty configuration. Error Correction enabled - not mandatory, but a good idea Data Compression - not required, but it helps, especially for text transfers. Auto Answer - If the SLIP connection is to be initiated from either machine, both modems should be set to auto answer, otherwise, just the answering modem. It is a good idea to configure the modem and then save the settings to NVRAM, so that the correct settings can always be restored by the slattach command. 4. UUCP configuration files /usr/lib/uucp/Devices /usr/lib/uucp/Dialers The Devices file must contain an entry with the tty and serial port speed used for the interface. In our example, Direct tty0 38400 slipdialer The keyword 'slipdialer' is merely an index into the Dialers file. For our purposes, the slipdialer entry in the Dialers file is simply: slipdialer This entry can also contain UUCP chat commands, or the chat commands can be included in the slattach command. 5. slattach invocation slattach connects the device on the tty port to the SLIP interface created by ifconfig, and sends any commands to the tty device if needed. For our example, remote.j.k.l would never initiate a call, only answer incoming calls. Therefore we execute: slattach tty0 38400 '"" ATZ OK ""' which connects the tty at 38400 baud. We could also simply run slattach tty0 ie. without any modem commands, but the modem to port speed may not be correctly set this way. In addition, the ATZ command ensures the modem is set to the NVRAM settings. On local.a.b.c type: slattach tty0 38400 '"" ATZ OK \pATDT4925871 BIS ""' 4 This establishes the link at 38400 baud, and executes the dial string as shown. The dial string is a UUCP chat string and are configured in an expect send expect send ... format. The string: '"" ATZ OK \pATDT4925871 BIS ""' is interpreted as: expect "" (null string) from modem send ATZ to modem expect OK from modem send \pATDT4925871 to modem expect BIS from modem BIS is the end of the CONNECT STRING. You could use any portion of the string returned by the modem upon a connection as the expect string. It may be wiser to simply expect CONNECT since all connections should return this string. The null strings are necessary because the first parameter of the UUCP is an expected string from the modem, which can only be a null string until the modem has been given a command. The last parameter (4) of the slattach command is the debug level. A debug level of 4 displays the UUCP chat strings, which is useful for checking the modem status. 6. Routing ifconfig is sufficient if all you want to do is talk between the two hosts. If you are running SLIP so that you can talk to more than just that one other host you have to advertise your address. 1) arp -s 802.5 iago 10:00:5a:b1:49:d8 pub where 802.5 is a token-ring network the hardware address can be obtained with `netstat -v` and iago was the SLIP client (My PC at home :) pub is the important part it means "published" You may want to run this at boot time. Routing through the SLIP link is similiar to routing of any gateway. Invoking the ifconfig command automatically sets up a route between the two SLIP machines. An entry in /etc/hosts or the named database should be made, with the same machine name used for the SLIP address as the ethernet address on each machine. For example, in /etc/hosts on remote.a.b.c (and any other machine on remote.a.b.c ethernet): 129.11.22.44 remote.a.b.c # ethernet address 129.11.22.1 remote.a.b.c # slip address It is preferable to place the ethernet address in the hosts file before the SLIP address so remote.a.b.c will resolve to the ethernet address. When using named, it is important to have both addresses in the reverse file with the same name. We experienced difficulties with NFS mounting over the slip link, owing to some machine interpreting NFS requests from one of the two SLIP machines as coming from the SLIP address, while the SLIP machine believed it was sending the request from the ethernet address. This problem was eliminated by having both addresses reverse resolve to the same name. 7. Performance At a modem speed of 14.4 kBaud and a port speed of 38.4 kBaud, we realized a transfer rate through ftp of about 3.5 kB/s for text files, and 1.3 kB/s for compressed files. ------------------------------ Subject: 1.607: Where is DCE discussed? DCE is the Distributed Computing Environment, which is roughly a flexible client-server architecture for heterogenous platforms. For more information, take a look in comp.soft-sys.dce. ------------------------------ Subject: 1.608: How do I make /var/spool/mail mountable? From: petersen@pi1.physik.uni-stuttgart.de (Joerg Petersen) In our cluster we share a /usr/local disk. We have a directory /usr/local/spool/mail and /var/spool/mail is soft-linked to it. From: fred@hal6000.thp.Uni-Duisburg.DE (Fred Hucht) Several problems has been reported on sharing the mail directory via NFS. The problems may occur when two or more sendmail daemons and/or mail readers access a user's mail file simultanously, because of NFS' file locking mechanism. We use another method here: Every user has one line in his/her $HOME/.forward file that reads xxx@mainserver.domain.name where xxx is the user node and mainserver.domain.name is the full hostname of one of the machines. Then all incoming mail to all machines is forwarded to mainserver, while mainserver ignores this line. ------------------------------ Subject: 1.609: getty spawning too rapidly From: aslam@abaseen.lums.edu.pk (Sohail Aslam) The problem can occur due a number of modem settings. The most frequent is that the echo is not disabled on modems that are to accept incoming calls. In hayes language, ATE0 disables echo. If echo is enabled, the login prompt sent by the DTE (computer) is echoed back to it. It then issues "password:" prompt which the modem conveniently echoes back again. And the cycle goes on. Another setting to check is the Q registers which controls the modem's response to the DTE. The hayes command ATQ0 enables results codes. The Q register in conjunction with the X and the V registers, reports back to the DTE the status of the incoming or outgoing call, and the type of connection established. For outgoing calls, one would want to enable result codes but not for incoming calls. If codes are enabled (via ATQ0), when a call comes in, the modem will send strings (if ATV1 and ATX4 set) "RINGING", "CONNECTED" etc. to the local DTE. The getty will think some one is trying to login. It will send password prompt. Trouble again. Telebit and other intelligent modems has ATQ2 setting which says "reports codes only when calling out." For others, you will need to disable it (ATQ1) and enable when calling out. The DSR setting can be a source of problem. Ideally, modem should raise DSR only when CD is detected and modem raises CTS. Computer, such as the VAX, wait 30 seconds after the modem raises DSR. If CD is not on by that time, the computer will drop DTR causing the modem to reset. The DSR should be set to be raised only when carrier has been detected. The hayes setting is AT&S1. The DCD setting should be such that it reflects the true nature of the carrier. The CD can be forced on at all times (AT&C0). This is not good. Set it to AT&C1. Most modems can reload saved settings from non-volatile memory on a DTR transition. This is useful for resetting the modem when a call drops. Use AT&D3 to get this effect. For dial in, thus, set AT E0 Q1 &C1 &D3 &S1 &W. The &W stores the settings in memory. They will be reloaded due to &D3. ------------------------------ Subject: 1.610: Does AIX support Compressed SLIP (CSLIP)? No. That means no VJ compression either :) See PPP in section 5.07 if you want more than standard SLIP. ------------------------------ Subject: 1.611: How do I setup anonymous ftp on my AIX system? (stolen from Peter Klee posting) Have a look at '/usr/lpp/tcpip/samples/anon.ftp'. It is a shell script and will set up a anonymous ftp site on your local RS/6000. Note: the ftpd that comes with AIX does not support the display messages every time a user changes a directory or even when they login. ------------------------------ Subject: 1.612: Talk, getting notification. If you are not getting notification (that someone wants to talk to you), use (swcons `tty` && mesg y) in one window. There are many variations of 'talk' and finding compatible versions for multiple operating systems can be tricky. ------------------------------ Subject: 1.613: Disabling software flow control; using RTS/CTS. Different versions of AIX 3.2.5 respond differently to attempts to enable flow control (RTS/CTS signals). This section is an attempt to compile a list of different approaches. The most straight forward is: chdev -l ttyxx -a rts=yes [ Note: ix40410 for AIX 3.2.5 should give you this functionality. PTF U426113 and numerous other superceding ptfs should provide this.] If carrier signal is high (its connected) you can try stty add rts strings /usr/lib/netsvc/yp/ypserv | head -2 @(#)16 1.12 com/cmd/usr.etc/yp/ypserv.c, cmdnfs, nfs325, 9334325a 5/4/93 19:44:41 If your AIX doesn't have securenets support, ask your support centre for the PTF which includes APAR IX32328. That seems to have included the securenets support. ------------------------------ Subject: 1.615: Why can't non-anonymous users login using WU-FTP? From: swcxt@boco.co.gov (Shane Castle) You must create a file named /etc/shells (this is the real /etc not a subdirectory of your false root), that contains all the shells that are defined on your system. Get the list from /etc/security/login.cfg. Also, if having proper group authentication is important to you, apply the following patch: --- ftpd.c.dist Wed Apr 13 15:17:18 1994 +++ ftpd.c Tue Jan 17 13:29:58 1995 @@ -1153,7 +1153,13 @@ setgroups(NULL, NULL); if (setpriv(PRIV_SET|PRIV_INHERITED|PRIV_EFFECTIVE|PRIV_BEQUEATH, &priv, sizeof(priv_t)) < 0 || - setuidx(ID_REAL|ID_EFFECTIVE, (uid_t)pw->pw_uid) < 0 || + initgroups(pw->pw_name, (gid_t)pw->pw_gid) < 0 || + setgidx(ID_REAL|ID_EFFECTIVE, (gid_t)pw->pw_gid) < 0 || + setegid((gid_t)pw->pw_gid) < 0) { + reply(550, "Can't set gid (AIX3)."); + goto bad; + } + if (setuidx(ID_REAL|ID_EFFECTIVE, (uid_t)pw->pw_uid) < 0 || seteuid((uid_t)pw->pw_uid) < 0) { reply(550, "Can't set uid (AIX3)."); goto bad; ------------------------------ Subject: 1.616: NIS users can't login, do I need '*' in /etc/passwd? From: ohnielse@fysik.dtu.dk (Ole Holm Nielsen) Aparently at least one version of AIX InfoExplorer suggests administrators use "+:*:0:0:::" as the last entry in the /etc/passwd file of NIS clients for security reasons. If the configuration SMIT is done using SMIT it will actually append "+::0:0:::" which works and does not compromise security. Using the '*' in the passwd field actaully prevents NIS users from logging in. "+::0:0:::" should not allow you to login as user "+" and without a password even when NIS is disabled, but it never hurts to double check. ------------------------------ Subject: 1.617: HP JetDirect cards and virtual printers? mkvirprt problems? (stolen from many) Since the release of AIX 3.2.5 adding a queue for JetDirect cards is as easy as creating a virtual printer using "smit mkvirprt" or mkvirprt. If the command hangs make sure you are using an HFT, aixterm or vt100 terminal. The entire procedure is available from the IBM FAX "Information Line" (800 IBM-4-FAX). From: Mark Bergman SMIT complains that some required software is not present on the system. It turns out that this software, "printers.hpJetDirect.attach (4.1.3.0)" is on the installation CD. HOWEVER, there is some bug somewhere, whereby the software may actually be already installed, but the system cannot see it. (Or maybe the bug is that the software is actually NOT installed, but the system in one place thinks it is! - I'm not sure). Therefore, use smit to look at Installed Software ("Software Installation and Maintenance", "Maintain Installed Software", "List Installed Software" and look at all software, then search through for "jet". If it finds it (i.e. it thinks that it is installed) - you must remove it (under smit's "Maintain Installed Software" level), and then reinstall from the CD! ------------------------------ Subject: 1.618: How can I hack libc.a to alter how hostnames are resolved? From: "L. Mark Larsen" [ Editors note: The implications of corrupting libc.a should not be understated. While recovering from a corrupt libc.a should be a matter of booting from floppy I wouldn't wish that on anyone with a supervisor or users to support :) Before you attempt this, you might want to read 2.07 first for advice on recovering from a destroyed or corrupted libc.a. Remember: backups are a VERY GOOD IDEA. enough of the weak kneed quivering... ] Nate Itkin (a colleague) is the individual who did the initial work. I suspect he would rather not be troubled with any questions you may have in this area and I can probably answer them just as easily. The motivation for this was to use DNS for MX records (we are using IDA sendmail) but NIS for most hostname lookups. Secondly, warnings: IBM has not given any sort of stamp of approval on what we have done (though they appear to have integrated resolv+ into AIX 4 based on some release notes I saw). While we have been using it successfully for about one year and have seen no problems, we can't and won't promise the same for you. This procedure plays around with libc.a which, as you probably know, is an XCOFF shared library under AIX and hence a critical part of the running system. You assume all the risk if you try to install this. All the usual disclaimers about liability, etc. apply - there is no warranty associated with any of this. Furthermore, know that any PTF you subsequently install that updates/replaces libc.a implies that you have to execute most of these procedures again. The details on how to use resolv+ under AIX 3 (it's only tested under 3.2.5 but should work for all point releases), have been moved to section 8.09. ------------------------------ Subject: 1.619: What modem settings do I need? ATQ2 - result codes in originate only AT&C1 - CD follows state of carrier AT&D2 - hangup on DTR drop ------------------------------ Subject: 1.620: NIS slave server config with master on different subnet? From: msidler@metronet.com (Mike Sidler) Assuming AIX 3.2.5,the master server up and running and the hosts file has the master name defined. On slave do: 1) domainname 2) startsrv -s ypserv 3) startsrv -s ypbind (ypwhich should return "loopback") 4) (/usr/sbin/)ypset -d (ypwhich should return "" 5) (/usr/sbin/)ypinit -s 6) Put "+::0:0:::" in /etc/passwd after last local login. Note: InfoExplorer has this entry INCORRECT in some versions. 7) Other cfg files (group, etc) may need configuring but this will get ypserv and ypbind running on the slave looking at the right stuff. ------------------------------ Subject: 1.621: Why does my 64 port concentrator loose data and drop the queue? [From: as@mynet.no (Arild Sletvold)] This problem has been associated with upgrading machines to 3.2.5. Try changing the values for the "Transmit buffer count" parameter in the printer/plotter setup in smit. You need to experiment with this parameter, to see which value that makes the printer print as fast as possible. If the value is too high, the printers will loose some of the data, and the queue will be disabled. If the value is too low, the printers will print very slowly. ------------------------------ Subject: 1.622: Netscape FastTrack server won't install on AIX 3.2.5 or 4.1. From: Cameron Ferstat Before installing FastTrack on an AIX 3.2.5 or 4.1 system, you must first install the AIX Shared Library Hookable Symbols/6000 Version 1.1.5.0, Reference RPQ No. P91153. (Note: This software should *not* be installed on an AIX 4.2 system!) If you try to install FastTrack on an AIX 3.2.5 or 4.1 system, without first installing the Hookable Symbols PRPQ, you will get the following error: > ./ns-setup 0509-037 System error - error data is: ./ns-setup 0509-022 Cannot load library libsvld.a[shr.o]. 0509-026 System error: A file or directory in the path name does not exist. You can download the installp image by anonymous ftp from . There is also an associated README.slhs file in that directory. ------------------------------ Subject: 1.623: How can I share files/printers with Windows 95? The freeware solution is Samba, available from . Commercial solutions include Fusion95 from Performance Technology and Syntax . ------------------------------ Subject: 1.624: Printing from AIX to WinNT/95/3.1 From: Charles J. Fisher 1. On your Windows system, share the printer. Assuming that you are running NT, make a user "root" with some password. 2. Get the Samba distribution from http://www.samba.org If you have a C compiler, get the source and compile it. If you don't have a C compiler, get a binary distribution for AIX. 3. Install Samba on AIX under /usr/local/samba. Specifically, make sure that /usr/local/samba/bin/smbclient is installed with execute rights for everyone. 4. You must also install a Samba configuration file under /usr/local/samba/lib/smb.conf If you intend to use your AIX as a file server for windows clients, you should modify smb.conf to accomplish this (see the Samba documentation). If you will be printing only, just use the sample smb.conf. 5. Make the directory /usr/local/samba/lib/printers 6. In that directory, install the following shell script as file "winprint": #!/bin/sh # This is a modification of the samba provided smbprint script # changed to work under AIX as the backend for a queue. It does # not read a config file. # # Variables below define the server and service. They are # the content of the .config file when printing from # /etc/printcap. # server="winserver" service="winprinter" user="root" password="root" # # Debugging log file, change to /dev/null if you like. # #logfile=/tmp/${USER}-print.log # # Some debugging help, change the >> to > if you want to save space. # #echo "server $server, service $service" >> $logfile #cat $1 | /usr/local/samba/bin/smbclient "\\\\$server\\$service" $password \ # -N -P -c 'print -' >> $logfile ( # NOTE You may wish to add the line `echo translate' if you want automatic # CR/LF translation when printing. echo translate echo "print -" cat $* ) | /usr/local/samba/bin/smbclient "\\\\$server\\$service" $password \ -U "$user" -N -P > /dev/null 7. The above file assumes that you are using \\winserver\winprinter as the printer share, and that the user is "root" and the password is "root". If this is not the case, modify the shell variable declarations. 8. Mark the file with execute permissions with "chmod 755 winprint" 9. Test the script with the command: "./winprint /etc/passwd" If everything is ok, your password file should be spooled to your windows printer. If it doesn't work, remove the "> /dev/null" from the last line of the script and rerun it. Examine the output of smbclient for clues. Clue #1: The Windows printer server is on the other side of a router. AIX is sending broadcast packets to find the Windows machine, which the router will not forward. You must find the Windows server's IP address and specify it with the "-I" parameter to smbclient, i.e. "-I 1.2.3.4". DHCP makes this situation even more complex. Clue #2: You username or password is wrong. smbclient will tell you about this if you free its output from > /dev/null. Clue #3: You might be violating shell quoting rules if you use special characters in the server or share name, password, etc. Don't use $, ", ', etc., or escape them properly. A password of ";rm -rf /" could be catastrophic. 10. Once the script can print files, it must be defined as a printer in the /etc/qconfig file. Add the following lines to the end of your /etc/qconfig: winprint: device = dwinprint up = TRUE discipline = sjn dwinprint: backend = /usr/local/samba/lib/printers/winprint 11. Test the printer with the following command: "lp -d winprint /etc/passwd" (Your password file should be printed again.) 12. You might examine the queue with the command "lpq -P winprint" or "lpstat -t" ------------------------------ Subject: 1.625: How do I get NFS mounting with Linux to work? Linux by default requires any NFS mount to use a so called reserved port below 1024 and AIX 4.3 does by default use ports above 1024. You can use the nfso command to restrict AIX to the reserved port range as follows: nfso -o nfs_use_reserved_ports=1 ------------------------------ Subject: 1.626: Telnet takes a 45 seconds to produce a prompt. This is in nearly all cases a DNS configuration problem, the AIX machine can not resolve the IP address of the node initiating the telnet connection. You can check the DNS reverse mapping by using the nslookup command on the IP number in question, this will probably timeout as well. Make sure that the nameserver lines in the /etc/resolv.conf file point to valid name servers. Some folks have reported that putting the following in /etc/netsvc.conf can help as well (see also Subject: 1.800): hosts=local,bind4 Getting a correct DNS Server configuration is the real answer. ------------------------------