OSA express gb adapter
I have an LPAR that shares a gb ethernet osa express adapter with OS/390 LPAR's. I am using SUSE distribution as it is the only one that I found that includes the OCO modules. I get the error that follows when setting up my network definition. I have on ocasion be able to get this to work, but 99% of the time it fails. Anybody have any ideas that might help me. Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' or auto for autoprobing (auto): Starting with microcode level 0146, OSA-Express QDIO require a portname to be set in the device driver. It identifies the port for sharing with other. OS images, for example the PORTNAME dataset used by OS/390. Do you have OSA Express microcode level 0146 or higher? y Note: If you share the card, you must use same portname on all guest/lpars using the card. Please enter the portname (must be 1 to 8 characters) to use: osa1 Using /lib/modules/2.4.7-SuSE-SMP/net/qeth.o qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.136.2.3 $/$Revision: 1 .53.2.2 $/$Revision: 1.18 $) qeth: allocated 0 spare buffers debug: qeth_setup: new level 3 debug: qeth_misc: new level 2 debug: qeth_data: new level 2 debug: qeth_control: new level 2 debug: qeth_sense: new level 2 debug: qeth_qerr: new level 2 debug: qeth_trace: new level 2 qeth: Trying to use card with devnos 0xC40/0xC41/0xC42 qeth: received an IDX TERMINATE on irq 0xAF4/0xAF5 with cause code 0x22 -- try another portname qeth: There were problems in hard-setting up the card. debug: unregistering qeth_setup debug: unregistering qeth_qerr debug: unregistering qeth_sense debug: unregistering qeth_misc debug: unregistering qeth_data debug: unregistering qeth_control debug: unregistering qeth_trace /lib/modules/2.4.7-SuSE-SMP/net/qeth.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters qeth module not loaded, module problem. Do you want to retry the qeth-setup (Yes/No) ? Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield [EMAIL PROTECTED]
Re: OSA express gb adapter
Upper and lower case gets the same result, also I have used specific device addresses as well as auto. Thanks Glen -Original Message- From: Malcolm Beattie [mailto:mbeattie@;clueful.co.uk] Sent: Wednesday, November 06, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: OSA express gb adapter Crowley, Glen L writes: > I have an LPAR that shares a gb ethernet osa express adapter with OS/390 > LPAR's. I am using SUSE distribution as it is the only one that I found > that includes the OCO modules. I get the error that follows when setting up > my network definition. I have on ocasion be able to get this to work, but > 99% of the time it fails. Anybody have any ideas that might help me. > > Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' > or auto for autoprobing (auto): > > Starting with microcode level 0146, OSA-Express QDIO require a portname to > be set in the device driver. It identifies the port for sharing with other. > OS images, for example the PORTNAME dataset used by OS/390. > Do you have OSA Express microcode level 0146 or higher? > y > Note: If you share the card, you must use same portname > on all guest/lpars using the card. > Please enter the portname (must be 1 to 8 characters) to use: > osa1 That name might be case-sensitive; I can't remember if I've ever tried without explicit uppercase so it's only a guess. Does trying "OSA1" in caps make a difference? > qeth: Trying to use card with devnos 0xC40/0xC41/0xC42 > qeth: received an IDX TERMINATE on irq 0xAF4/0xAF5 with cause code 0x22 -- > try > another portname Are those device numbers right for the card you were intending to use? If anyone adds another OSA to your LPAR without telling you, you may end up with the wrong one. It might be safer to give the triple of device numbers explicitly at the "Enter the device addresses" prompt instead of letting it autodetect. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
Re: OSA express gb adapter
OSA1 is what is defined in the VTAM TRLE and caps does not make a difference. Glen -Original Message- From: Mark Kliner [mailto:MarkK@;VSP.com] Sent: Wednesday, November 06, 2002 9:37 AM To: [EMAIL PROTECTED] Subject: Re: OSA express gb adapter Is that indeed the same portname defined in the VTAM TRLE setup under OS/390? Does it need to be specified as upper-case? Mark Kliner Systems Programmer Vision Service Plan Rancho Cordova, CA -Original Message- From: Crowley, Glen L [mailto:GLCROWLEY@;arkbluecross.com] Sent: Wednesday, November 06, 2002 7:15 AM To: [EMAIL PROTECTED] Subject: OSA express gb adapter I have an LPAR that shares a gb ethernet osa express adapter with OS/390 LPAR's. I am using SUSE distribution as it is the only one that I found that includes the OCO modules. I get the error that follows when setting up my network definition. I have on ocasion be able to get this to work, but 99% of the time it fails. Anybody have any ideas that might help me. Enter the device addresses for the qeth module, e.g. '0xf800,0xf801,0xf802' or auto for autoprobing (auto): Starting with microcode level 0146, OSA-Express QDIO require a portname to be set in the device driver. It identifies the port for sharing with other. OS images, for example the PORTNAME dataset used by OS/390. Do you have OSA Express microcode level 0146 or higher? y Note: If you share the card, you must use same portname on all guest/lpars using the card. Please enter the portname (must be 1 to 8 characters) to use: osa1 Using /lib/modules/2.4.7-SuSE-SMP/net/qeth.o qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.136.2.3 $/$Revision: 1 .53.2.2 $/$Revision: 1.18 $) qeth: allocated 0 spare buffers debug: qeth_setup: new level 3 debug: qeth_misc: new level 2 debug: qeth_data: new level 2 debug: qeth_control: new level 2 debug: qeth_sense: new level 2 debug: qeth_qerr: new level 2 debug: qeth_trace: new level 2 qeth: Trying to use card with devnos 0xC40/0xC41/0xC42 qeth: received an IDX TERMINATE on irq 0xAF4/0xAF5 with cause code 0x22 -- try another portname qeth: There were problems in hard-setting up the card. debug: unregistering qeth_setup debug: unregistering qeth_qerr debug: unregistering qeth_sense debug: unregistering qeth_misc debug: unregistering qeth_data debug: unregistering qeth_control debug: unregistering qeth_trace /lib/modules/2.4.7-SuSE-SMP/net/qeth.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters qeth module not loaded, module problem. Do you want to retry the qeth-setup (Yes/No) ? Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield [EMAIL PROTECTED]
OSA express gb adapter
Thanks to those who replied to my message. Apparently, if you don't reply with the portname in upper case the first time thru the questions, it does not matter on the 2nd trip thru. If I enter the portname in upper case the first time thru, all works ok. Thanks Glen I have an LPAR that shares a gb ethernet osa express adapter with OS/390 LPAR's. I am using SUSE distribution as it is the only one that I found that includes the OCO modules. I get the error that follows when setting up my network definition. I have on ocasion be able to get this to work, but 99% of the time it fails. Anybody have any ideas that might help me. Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield [EMAIL PROTECTED]
smbclient authorization error
I am running cups 1.1.15 and samba 2.2.7 on SuSE 7 for s390. Trying to run cupsaddsmb to copy drivers files. I get an error creating the directory to copy the drivers to. I am running as root. Root has been added to the smbpasswd file. I put this on the samba listserv with no response. If anybody has been here or has a suggestion, please respond. linuxi:/ # cupsaddsmb -v -U root im_hp4 Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir W32X86;put /var/spool/cups/tmp/3dee0e300f548 W32X86/im_hp4.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \W32X86 ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPS5.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.HLP Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir WIN40;put /var/spool/cups/tmp/3dee0e300f548 WIN40/im_hp4.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \WIN40 ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADFONTS.MFM ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.DRV ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.HLP ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/DEFPRTR2.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ICONLIB.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/PSMON.DLL Running command: rpcclient localhost -N -U'root%linux' -c 'adddriver "Windows NT x86" "im_hp4:ADOBEPS5.DLL:im_hp4.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"' session setup ok Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] result was NT_STATUS_ACCESS_VIOLATION Running command: rpcclient localhost -N -U'root%linux' -c 'adddriver "Windows 4.0" "im_hp4:ADOBEPS4.DRV:im_hp4.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM, DEFPRTR2.PPD,ICONLIB.DLL"' session setup ok Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] result was NT_STATUS_INVALID_INFO_CLASS Running command: rpcclient localhost -N -U'root%linux' -c 'setdriver im_hp4 im_hp4' session setup ok Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] SetPrinter call failed! result was NT_STATUS_ACCESS_VIOLATION Thanks Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield [EMAIL PROTECTED]
Re: smbclient authorization error
Here is a copy of my smb.conf file. # Samba config file created using SWAT # from lrd1ssl2.abcbs.net (192.168.5.53) # Date: 2002/11/19 14:19:51 # Global parameters [global] workgroup = ABCBSNET netbios name = LINUXI.ABCBS.NET security = none map to guest = Bad User keepalive = 30 os level = 2 wins server = 192.168.1.12 kernel oplocks = No template shell = /bin/bash printcap name = cups printing = cups load printers = yes [homes] comment = home-directory read only = No create mask = 0750 browseable = No [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No public = yes writeable = no [print$] path = /etc/samba/drivers browseable = yes guest ok = Yes read only = yes write list = root [linuxi_tmp] path = /tmp guest ok = Yes [im_hp4] path = /tmp printable = Yes [im_clj4500] path = /tmp printable = Yes Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:16 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Glen, What does your smb.conf file say about who has write access to that resource? Any access request has to pass both UNIX permissions and Samba permissions testing. Mark Post -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:45 AM To: [EMAIL PROTECTED] Subject: smbclient authorization error I am running cups 1.1.15 and samba 2.2.7 on SuSE 7 for s390. Trying to run cupsaddsmb to copy drivers files. I get an error creating the directory to copy the drivers to. I am running as root. Root has been added to the smbpasswd file. I put this on the samba listserv with no response. If anybody has been here or has a suggestion, please respond. linuxi:/ # cupsaddsmb -v -U root im_hp4 Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir W32X86;put /var/spool/cups/tmp/3dee0e300f548 W32X86/im_hp4.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \W32X86 ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPS5.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.HLP Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir WIN40;put /var/spool/cups/tmp/3dee0e300f548 WIN40/im_hp4.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \WIN40 ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADFONTS.MFM ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.DRV ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.HLP ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/DEFPRTR2.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ICONLIB.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/PSMON.DLL Running command: rpcclient localhost -N -U'root%linux' -c 'adddriver "Windows NT x86" "im_hp4:ADOBEPS5.DLL:im_hp4.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"' session setup ok Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] result was NT_STATUS_ACCESS_VIOLATION Running command: rpcclient localhost -N -U'root%linux' -c 'adddriver "Windows 4.0" "im_hp4:ADOBEPS4.
Re: smbclient authorization error
I commented them out as suggested, but the result of the cupsaddsmb is the same. Glen -Original Message- From: Marist EDU [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:38 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error The share print$ is set to "read only" I would comment out both that and the write list to see if we can get it working first. Josh -Original Message----- From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:28 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Here is a copy of my smb.conf file. # Samba config file created using SWAT # from lrd1ssl2.abcbs.net (192.168.5.53) # Date: 2002/11/19 14:19:51 # Global parameters [global] workgroup = ABCBSNET netbios name = LINUXI.ABCBS.NET security = none map to guest = Bad User keepalive = 30 os level = 2 wins server = 192.168.1.12 kernel oplocks = No template shell = /bin/bash printcap name = cups printing = cups load printers = yes [homes] comment = home-directory read only = No create mask = 0750 browseable = No [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No public = yes writeable = no [print$] path = /etc/samba/drivers browseable = yes guest ok = Yes read only = yes write list = root [linuxi_tmp] path = /tmp guest ok = Yes [im_hp4] path = /tmp printable = Yes [im_clj4500] path = /tmp printable = Yes Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:16 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Glen, What does your smb.conf file say about who has write access to that resource? Any access request has to pass both UNIX permissions and Samba permissions testing. Mark Post -Original Message----- From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:45 AM To: [EMAIL PROTECTED] Subject: smbclient authorization error I am running cups 1.1.15 and samba 2.2.7 on SuSE 7 for s390. Trying to run cupsaddsmb to copy drivers files. I get an error creating the directory to copy the drivers to. I am running as root. Root has been added to the smbpasswd file. I put this on the samba listserv with no response. If anybody has been here or has a suggestion, please respond. linuxi:/ # cupsaddsmb -v -U root im_hp4 Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir W32X86;put /var/spool/cups/tmp/3dee0e300f548 W32X86/im_hp4.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \W32X86 ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPS5.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.HLP Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir WIN40;put /var/spool/cups/tmp/3dee0e300f548 WIN40/im_hp4.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \WIN40 ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADFONTS.MFM ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.DRV ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN40/ADOBEPS4.HLP ERRDOS - ERRnoaccess (Access denied.) opening remote file \WIN4
Re: smbclient authorization error
Would root not have permission to an directory and the files within. I thought that is why the command is run as root. Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:57 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Josh, That's not the problem, I don't think. My print$ share is also defined as read only, with a write list, and I can write to it, assuming the proper UNIX permissions. Mark Post -Original Message- From: Marist EDU [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 10:38 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error The share print$ is set to "read only" I would comment out both that and the write list to see if we can get it working first. Josh -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:28 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Here is a copy of my smb.conf file. # Samba config file created using SWAT # from lrd1ssl2.abcbs.net (192.168.5.53) # Date: 2002/11/19 14:19:51 # Global parameters [global] workgroup = ABCBSNET netbios name = LINUXI.ABCBS.NET security = none map to guest = Bad User keepalive = 30 os level = 2 wins server = 192.168.1.12 kernel oplocks = No template shell = /bin/bash printcap name = cups printing = cups load printers = yes [homes] comment = home-directory read only = No create mask = 0750 browseable = No [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No public = yes writeable = no [print$] path = /etc/samba/drivers browseable = yes guest ok = Yes read only = yes write list = root [linuxi_tmp] path = /tmp guest ok = Yes [im_hp4] path = /tmp printable = Yes [im_clj4500] path = /tmp printable = Yes Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:16 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Glen, What does your smb.conf file say about who has write access to that resource? Any access request has to pass both UNIX permissions and Samba permissions testing. Mark Post -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 9:45 AM To: [EMAIL PROTECTED] Subject: smbclient authorization error I am running cups 1.1.15 and samba 2.2.7 on SuSE 7 for s390. Trying to run cupsaddsmb to copy drivers files. I get an error creating the directory to copy the drivers to. I am running as root. Root has been added to the smbpasswd file. I put this on the samba listserv with no response. If anybody has been here or has a suggestion, please respond. linuxi:/ # cupsaddsmb -v -U root im_hp4 Password for root required to access localhost via SAMBA: Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir W32X86;put /var/spool/cups/tmp/3dee0e300f548 W32X86/im_hp4.PPD;put /usr/share/cups/drivers/ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLL W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined by the TID or the UID.) making remote directory \W32X86 ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/im_hp4.PPD ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPS5.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.DLL ERRDOS - ERRnoaccess (Access denied.) opening remote file \W32X86/ADOBEPSU.HLP Running command: smbclient //localhost/print\$ -N -U'root%linux' -c 'mkdir WIN40;put /var/spool/cups/tmp/3dee0e300f548 WIN40/im_hp4.PPD;put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' added interface ip=172.16.14.101 bcast=172.16.14.255 nmask=255.255.255.0 Domain=[ABCBSNET] OS=[Unix] Server=[Samba 2.2.7] ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested function. The context is defined b
Re: smbclient authorization error
Mark This is the log after making the change suggested. It looks as user "nobody" is trying to do the work. Where might I be picking that up from. [2002/12/04 10:37:39, 1] smbd/service.c:make_connection(636) linuxi (127.0.0.1) connect to service print$ as user root (uid=0, gid=0) (pid 4832) [2002/12/04 10:37:39, 1] smbd/service.c:close_cnum(677) linuxi (127.0.0.1) closed connection to service print$ [2002/12/04 10:37:39, 1] smbd/service.c:make_connection(636) linuxi (127.0.0.1) connect to service print$ as user root (uid=0, gid=0) (pid 4834) [2002/12/04 10:37:39, 1] smbd/service.c:close_cnum(677) linuxi (127.0.0.1) closed connection to service print$ [2002/12/04 10:37:40, 1] smbd/service.c:make_connection(636) linuxi (127.0.0.1) connect to service print$ as user nobody (uid=65534, gid=65534) (pid 4836) [2002/12/04 10:37:40, 1] smbd/service.c:close_cnum(677) linuxi (127.0.0.1) closed connection to service print$ [2002/12/04 10:37:40, 1] smbd/service.c:make_connection(636) linuxi (127.0.0.1) connect to service print$ as user nobody (uid=65534, gid=65534) (pid 4838) [2002/12/04 10:37:40, 0] printing/nt_printing.c:move_driver_to_download_area(1475) move_driver_to_download_area: Unable to rename [WIN40/ADOBEPS4.DRV] to [WIN40/0/ADOBEPS4.DRV] [2002/12/04 10:37:40, 1] smbd/service.c:close_cnum(677) linuxi (127.0.0.1) closed connection to service print$ Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 10:23 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error Oddly enough, testparm does _not_ complain about that. It just ignores it and defaults to security = user. (Which is what I would have recommended anyway.) One other possibility is that the password being supplied is not validating properly, either because of a typo, or whatever, and the "map to bad user" is taking affect. Try setting your log level to 1 (or higher) and kill -1 all your smbd instances (killall -1 smbd should do it). Then try it again, and see what shows up in your log file. You'll also have to add a "log file = /var/log/samba.%m" parameter to smb.conf. The log file that shows up should be netbiosname.smbd. You should probably also change the netbios name parameter to a proper one with one node only, perhaps just "LINUXI". Mark Post -Original Message- From: Daniel Jarboe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 11:08 AM To: [EMAIL PROTECTED] Subject: Re: smbclient authorization error I think your problem is with your security = none line. Does testparm say this is okay? man smb.conf lists 4 valid settings: share, user, server, domain. I just checked swat, and it has a drop-down box with only those 4 settings. I'd start with security = user , and if that is too restrictive then drop to security = share. HTH ~ Daniel From: Crowley, Glen L Sent: Wednesday, December 04, 2002 10:28 AM Subject: Re: smbclient authorization error Here is a copy of my smb.conf file. # Samba config file created using SWAT # from lrd1ssl2.abcbs.net (192.168.5.53) # Date: 2002/11/19 14:19:51 # Global parameters [global] workgroup = ABCBSNET netbios name = LINUXI.ABCBS.NET security = none map to guest = Bad User keepalive = 30 os level = 2 wins server = 192.168.1.12 kernel oplocks = No template shell = /bin/bash printcap name = cups printing = cups load printers = yes [homes] comment = home-directory read only = No create mask = 0750 browseable = No [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No public = yes writeable = no [print$] path = /etc/samba/drivers browseable = yes guest ok = Yes read only = yes write list = root [linuxi_tmp] path = /tmp guest ok = Yes [im_hp4] path = /tmp printable = Yes [im_clj4500] path = /tmp printable = Yes Glen --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Debian cant find OSA adapter files
I have installed Debian "woody" with the IBM OCO QETH and QDIO modules for 2.4.17. Installation went fine and able to telnet in and to do install. Upon booting from dasd the first time, I get the following error: Setting up IP spoofing protection: rp_filter. Configuring network interfaces: modprobe: modprobe: Can't locate module eth0 SIOCSIFADDR: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device modprobe: modprobe: Can't locate module eth0 SIOCSIFNETMASK: No such device modprobe: modprobe: Can't locate module eth0 SIOCSIFBRDADDR: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device done. The parms used at OSA setup are add_parms,0x10,0xc40,0xc42,portname=OSA1 qeth,0xc40,0xc41,0xc42 have also tried eth0,0xc40,0xc41,0xc42 Anybody been here or have any suggestions? Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield 501-378-2432 [EMAIL PROTECTED]
Re: Debian cant find OSA adapter files
cat /etc/modules.conf ### This file is automatically generated by update-modules" # # Please do not edit this file directly. If you want to change or add # anything please take a look at the files in /etc/modutils and read # the manpage for update-modules. # ### update-modules: start processing /etc/modutils/0keep # DO NOT MODIFY THIS FILE! # This file is not marked as conffile to make sure if you upgrade modutils # it will be restored in case some modifications have been made. # # The keep command is necessary to prevent insmod and friends from ignoring # the builtin defaults of a path-statement is encountered. Until all other # packages use the new `add path'-statement this keep-statement is essential # to keep your system working keep ### update-modules: end processing /etc/modutils/0keep ### update-modules: start processing /etc/modutils/actions # Special actions that are needed for some modules # The BTTV module does not load the tuner module automatically, # so do that in here post-install bttv insmod tuner post-remove bttv rmmod tuner ### update-modules: end processing /etc/modutils/actions ### update-modules: start processing /etc/modutils/aliases # Aliases to tell insmod/modprobe which modules to use # Uncomment the network protocols you don't want loaded: # alias net-pf-1 off# Unix # alias net-pf-2 off# IPv4 # alias net-pf-3 off# Amateur Radio AX.25 # alias net-pf-4 off# IPX # alias net-pf-5 off# DDP / appletalk # alias net-pf-6 off# Amateur Radio NET/ROM # alias net-pf-9 off# X.25 # alias net-pf-10 off # IPv6 # alias net-pf-11 off # ROSE / Amateur Radio X.25 PLP # alias net-pf-19 off # Acorn Econet alias char-major-10-175 agpgart alias char-major-10-200 tun alias char-major-81 bttv alias char-major-108ppp_generic alias /dev/ppp ppp_generic alias tty-ldisc-3 ppp_async alias tty-ldisc-14 ppp_synctty alias ppp-compress-21 bsd_comp alias ppp-compress-24 ppp_deflate alias ppp-compress-26 ppp_deflate # Crypto modules (see http://www.kerneli.org/) alias loop-xfer-gen-0 loop_gen alias loop-xfer-3 loop_fish2 alias loop-xfer-gen-10 loop_gen alias cipher-2 des alias cipher-3 fish2 alias cipher-4 blowfish alias cipher-6 idea alias cipher-7 serp6f alias cipher-8 mars6 alias cipher-11 rc62 alias cipher-15 dfc2 alias cipher-16 rijndael alias cipher-17 rc5 ### update-modules: end processing /etc/modutils/aliases ### update-modules: start processing /etc/modutils/paths # This file contains a list of paths that modprobe should scan, # beside the once that are compiled into the modutils tools # themselves. ### update-modules: end processing /etc/modutils/paths ### update-modules: start processing /etc/modutils/qeth-2.4.17-s390-3 alias eth0 qeth-2.4.17-s390-3 ### update-modules: end processing /etc/modutils/qeth-2.4.17-s390-3 ### update-modules: start processing /etc/modutils/arch/s390 # # /etc/modutils/arch/s390 # # For details concering configuration options of S/390 specific drivers # see the "LINUX for S/390 Device Drivers and Installation Commands" book # on http://oss.software.ibm.com/developerworks/opensource/linux390/docu.html # alias tr0lcs #alias eth0 lcs alias eth0 qeth alias ctc0 ctc alias escon0 ctc alias iucv0 netiucv ### update-modules: end processing /etc/modutils/arch/s390 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 1:23 PM To: [EMAIL PROTECTED] Subject: Re: Debian cant find OSA adapter files What is in /etc/modules.conf? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Crowley, Glen L Sent: Wednesday, December 18, 2002 2:00 PM To: [EMAIL PROTECTED] Subject: Debian cant find OSA adapter files I have installed Debian "woody" with the IBM OCO QETH and QDIO modules for 2.4.17. Installation went fine and able to telnet in and to do install. Upon booting from dasd the first time, I get the following error: Setting up IP spoofing protection: rp_filter. Configuring network interfaces: modprobe: modprobe: Can't locate module eth0 SIOCSIFADDR: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device modprobe: modprobe: Can't locate module eth0 SIOCSIFNETMASK: No such device modprobe: modprobe: Can't locate module eth0 SIOCSIFBRDADDR: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device modprobe: modprobe: Can't locate module eth0 eth0: ERROR while getting interface flags: No such device done. The parms used at OSA setup are add_parms,0x10,0xc40,0xc42,portname=OSA1 qeth,0xc40,0xc41,0xc42 have also tried eth0,0xc40,0xc41,0xc42 Anybody been he
Re: Debian cant find OSA adapter files
I missed typed it in the email, during the install I used portname:OSA1 Glen -Original Message- From: Daniel Jarboe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 1:20 PM To: [EMAIL PROTECTED] Subject: Re: Debian cant find OSA adapter files Should be portname: , not portname= ... From recent traffic on this list, that and add_parms seem to be commonly mistyped. ~ Daniel > -Original Message- > From: Crowley, Glen L [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 18, 2002 2:00 PM > To: [EMAIL PROTECTED] > Subject: Debian cant find OSA adapter files > > > I have installed Debian "woody" with the IBM OCO QETH and > QDIO modules for > 2.4.17. Installation went fine and able to telnet in and to > do install. > Upon booting from dasd the first time, I get the following error: > Setting up IP spoofing protection: rp_filter. > Configuring network interfaces: > modprobe: modprobe: Can't locate module eth0 > SIOCSIFADDR: No such device > modprobe: modprobe: Can't locate module eth0 > eth0: ERROR while getting interface flags: No such device > modprobe: modprobe: Can't locate module eth0 > SIOCSIFNETMASK: No such device > modprobe: modprobe: Can't locate module eth0 > SIOCSIFBRDADDR: No such device > modprobe: modprobe: Can't locate module eth0 > eth0: ERROR while getting interface flags: No such device > modprobe: modprobe: Can't locate module eth0 > eth0: ERROR while getting interface flags: No such device > done. > > The parms used at OSA setup are > > add_parms,0x10,0xc40,0xc42,portname=OSA1 > qeth,0xc40,0xc41,0xc42 have also tried eth0,0xc40,0xc41,0xc42 > > Anybody been here or have any suggestions? > > Glen Crowley > Lead Systems Programmer > Arkansas Blue Cross Blue Shield > 501-378-2432 > [EMAIL PROTECTED] > > --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Re: Debian cant find OSA adapter files
Thank you for the message. I changed my script to create the ramdisk and thing work much better now. Glen -Original Message- From: Gerhard Tonn [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 6:51 AM To: [EMAIL PROTECTED] Subject: Re: Debian cant find OSA adapter files >### update-modules: end processing /etc/modutils/paths >### update-modules: start processing /etc/modutils/qeth-2.4.17-s390-3 >alias eth0 qeth-2.4.17-s390-3 >### update-modules: end processing /etc/modutils/qeth-2.4.17-s390-3 >### update-modules: start processing /etc/modutils/arch/s390 This seems to be a problem with the installation script. It assumes that the name of the OCO module is qeth.o. You only need to rename the OCO module from Developer Works before building the second ramdisk. BTW., you find a script at http://www.trustsec.de/deb390/modules.php?op=modload&name=Downloads&file=ind ex&req=viewdownload&cid=5 that does exactly that before creating the ramdisk. Regards, Gerhard
SAMBA server not seen from network neighborhood
I have Samba 2.2.8 running on Debian Woody for S390. I am trying to connect via the wins server list that is on a win 2000 wins server, but I don't see my linux server in the list. I can ping and search and find the server by name. I looked in the log.nmdb for messages, but the file is not being created. Following is my smb.conf file # Samba config file created using SWAT # from 172.16.55.21 (172.16.55.21) # Date: 2003/03/19 13:33:45 # Global parameters [global] security = user workgroup = ABCBSNET server string = LINUX3 log level = 5 log file = /var/log/samba/log.%m max log size = 1000 printcap name = cups wins server = 172.16.6.11 printing = cups [public] path = /home/public valid users = +usergroup read only = No create mask = 0660 directory mask = 0770 [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No [print$] comment = printer drivers path = /etc/samba/drivers write list = root [infmgmt_cj4600c] path = /tmp guest ok = Yes printable = Yes [micclj01] path = /tmp guest ok = Yes printable = Yes Question 1 is does anyone know why I am not seeing my server from the WINS world? Question 2 is does anyone know why I am not getting the nmdb log file (smdb is logging ok)? Samba 2.2.7 was having the same problem, so I upgraded to 2.2.8 to see if it would do better. Thanks Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield 501-378-2432 [EMAIL PROTECTED]
Re: SAMBA server not seen from network neighborhood
My nmdb is running or so swat and ps -ef say. I am connected via a OSA express adapter. Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:10 PM To: [EMAIL PROTECTED] Subject: Re: SAMBA server not seen from network neighborhood Is nmbd actually running? What is your network connection? CTC? IUCV? Guest LAN? Mark Post -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:42 PM To: [EMAIL PROTECTED] Subject: SAMBA server not seen from network neighborhood I have Samba 2.2.8 running on Debian Woody for S390. I am trying to connect via the wins server list that is on a win 2000 wins server, but I don't see my linux server in the list. I can ping and search and find the server by name. I looked in the log.nmdb for messages, but the file is not being created. Following is my smb.conf file # Samba config file created using SWAT # from 172.16.55.21 (172.16.55.21) # Date: 2003/03/19 13:33:45 # Global parameters [global] security = user workgroup = ABCBSNET server string = LINUX3 log level = 5 log file = /var/log/samba/log.%m max log size = 1000 printcap name = cups wins server = 172.16.6.11 printing = cups [public] path = /home/public valid users = +usergroup read only = No create mask = 0660 directory mask = 0770 [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No [print$] comment = printer drivers path = /etc/samba/drivers write list = root [infmgmt_cj4600c] path = /tmp guest ok = Yes printable = Yes [micclj01] path = /tmp guest ok = Yes printable = Yes Question 1 is does anyone know why I am not seeing my server from the WINS world? Question 2 is does anyone know why I am not getting the nmdb log file (smdb is logging ok)? Samba 2.2.7 was having the same problem, so I upgraded to 2.2.8 to see if it would do better. Thanks Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield 501-378-2432 [EMAIL PROTECTED]
Re: SAMBA server not seen from network neighborhood
Mark Testparm runs ok and I don't see any conflicts in its list. Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:29 PM To: [EMAIL PROTECTED] Subject: Re: SAMBA server not seen from network neighborhood Well, that eliminates a few possibilities. Do you get any error messages from "testparm" ? Mark Post -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 3:18 PM To: [EMAIL PROTECTED] Subject: Re: SAMBA server not seen from network neighborhood My nmdb is running or so swat and ps -ef say. I am connected via a OSA express adapter. Glen -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:10 PM To: [EMAIL PROTECTED] Subject: Re: SAMBA server not seen from network neighborhood Is nmbd actually running? What is your network connection? CTC? IUCV? Guest LAN? Mark Post -Original Message- From: Crowley, Glen L [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:42 PM To: [EMAIL PROTECTED] Subject: SAMBA server not seen from network neighborhood I have Samba 2.2.8 running on Debian Woody for S390. I am trying to connect via the wins server list that is on a win 2000 wins server, but I don't see my linux server in the list. I can ping and search and find the server by name. I looked in the log.nmdb for messages, but the file is not being created. Following is my smb.conf file # Samba config file created using SWAT # from 172.16.55.21 (172.16.55.21) # Date: 2003/03/19 13:33:45 # Global parameters [global] security = user workgroup = ABCBSNET server string = LINUX3 log level = 5 log file = /var/log/samba/log.%m max log size = 1000 printcap name = cups wins server = 172.16.6.11 printing = cups [public] path = /home/public valid users = +usergroup read only = No create mask = 0660 directory mask = 0770 [printers] comment = All Printers path = /var/spool/samba printer admin = root guest ok = Yes printable = Yes browseable = No [print$] comment = printer drivers path = /etc/samba/drivers write list = root [infmgmt_cj4600c] path = /tmp guest ok = Yes printable = Yes [micclj01] path = /tmp guest ok = Yes printable = Yes Question 1 is does anyone know why I am not seeing my server from the WINS world? Question 2 is does anyone know why I am not getting the nmdb log file (smdb is logging ok)? Samba 2.2.7 was having the same problem, so I upgraded to 2.2.8 to see if it would do better. Thanks Glen Crowley Lead Systems Programmer Arkansas Blue Cross Blue Shield 501-378-2432 [EMAIL PROTECTED]
Re: SAMBA server not seen from network neighborhood
The listening ports ar good.
When I run the smbclient, my linux system shows as the master for the
ABCBSNET workgroup.
WorkgroupMaster
----
ABCBS-ACTUARIAL ACTUARIAL-BASE
ABCBSIVR
ABCBSNET LINUX3 < I would expect this
to be my WINS server
BCBSAR LRD1DATAMOVER1
BRDFIREWALL BRD1PRX1
DS LRD1DS1
DSDEVLRD1DS5
EMC BLAST1
EXTDNS DNS1
FISNTGROUP ACTUARIAL_BDC2
LABNET BRD1PDC1
PHRECNET LRD1UNIFY1
PRINTSHOPEX2000
TANT-A01 EVEJA02A
WORKGROUPACCESSMACH
I changed the local master value to no, but it made no difference. Any
options I need to change to correct this.
My Wins server is win2000.
Glen
-Original Message-
From: Tzafrir Cohen [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 11:08 AM
To: [EMAIL PROTECTED]
Subject: Re: SAMBA server not seen from network neighborhood
On Wed, Mar 19, 2003 at 02:18:06PM -0600, Crowley, Glen L wrote:
> My nmdb is running or so swat and ps -ef say. I am connected via a OSA
> express adapter.
Is it actually listening on the relevant ports? Run as root:
netstat -nlup |grep 13[78]
And see if you see a process "nmbd" on both port 137 and port 138 (this
is udp).
Try connecting from your system:
smbclient -L linux3 -U %
('-U %' is for guest login)
Alternatively, you may need to login with a valid user.
What OS exactly is the wins server? Is it part of a domain?
Try increasing the debug value in smb.conf, and then go again through
the logs.
And as a last resort: try stopping the nmbd, and running it manually.
See with what switches it runs (use ps auxww|grep nmb), remove the option
'-D' and add '-i'.
See if it throws any really nasty warnings about not being able to write
logs file and thus quiting (or whatever).
--
Tzafrir Cohen +---+
http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend|
mailto:[EMAIL PROTECTED] +---+
Re: SAMBA server not seen from network neighborhood
I get the following when I run the smbcontrol linux3:/# smbcontrol 11533 debug 1 tdb((null)): tdb_open_ex: could not open file /var/run/samba/connections.tdb: No such file or directory Failed to open connections database in send_message. linux3:/# Glen -Original Message- From: Daniel Jarboe [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 2:58 PM To: [EMAIL PROTECTED] Subject: Re: SAMBA server not seen from network neighborhood Does a "smbcontrol pid-of-nmbd debug 1" cause a log.nmbd to be written? If so, anything interesting dumped to it with a "kill -HUP pid-of-nmbd" ? > Testparm runs ok and I don't see any conflicts in its list. > > Glen ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
