Solaris Clients

I am trying to integrate Solaris clients to our Open Directory LDAP server..
Im am following this:
http://74.125.39.104/search?q=cache:ILu9oe8Veg0J:www.jerkys.org/wiki/pages/viewp age.action%3FpageId%3D2031736%22solaris+10%22+%22opendirectory%22&hl=de&ct=clnk&cd=12
and that:
http://discussions.apple.com/thread.jspa?threadID=382600
articles, but dow not have any success with Solaris 10 and MacOSX 10.5.
I get the following error:
Starting network services
start: /usr/bin/domainname borg.loopback.org... success
start: sleep 17700000 microseconds
start: network/ldap/client:default... timed out
start: network/ldap/client:default... offline to disable
stop: sleep 100000 microseconds
when calling:
[root@zion ># ldapclient manual -v -a domainName=borg.loopback.org -a serviceSearchDescriptor=passwd:cn=users,dc=borg.loopback,dc=org -a serviceSearchDescriptor=group:cn=groups,dc=borg.loopback,dc=org -a authenticationMethod=none -a credentialLevel=proxy -a defaultSearchBase=dc=loopback,dc=org -a searchTimeLimit=60 -a proxyDN=uid=root,cn=users,dc=borg,dc=loopback,dc=org -a proxyPassword=XXX borg.loopback.org
Previously, I copied over /etc/krb5/krb5.conf from OD-server's /Library/Preferences/edu.mit.Kerberos von Borg
an created a keytab file which I copied to /etc/krb5/krb5.keytab.
Does anyone have I working receipe here ?
Best thanks,
-Jan

This one works:
# ldapclient manual -a credentialLevel=self -a authenticationMethod=sasl/gssapi -a domainName=loopback.org -a serviceSearchDescriptor=passwd:cn=users,dc=loopback,dc=org -a serviceSearchDescriptor=group:cn=groups,dc=loopback,dc=org -a defaultSearchBase=dc=loopback,dc=org -a searchTimeLimit=60 ldap.loopback.org

Similar Messages

  • Solaris client 11g R2 won't unzip

    I have downloaded the Solaris client (32 and 64 bit) files twice today- once to Windows and once directly to a Solaris server. These files cannot be unzipped. When will usable files be available? Thanks.

    kmcswain wrote:
    I have downloaded the Solaris client (32 and 64 bit) files twice today- once to Windows and once directly to a Solaris server. These files cannot be unzipped. When will usable files be available? Thanks.Have you confirmed the checksum (cksum). And did you try other files and were they successful? I have downloaded database .zip to a linux box and (unzip -t) seems successful.
    Edited by: bigdelboy on 09-Nov-2009 14:32 Have now downloaded both Sparc 11gR2 32/64 clients .zip (uk) and unizp -t working fine for me from OEL5u4 ...

  • Invoking Web Forms from Sun Solaris Client PC

    HI,
    Can any one tell me whether we can invoke Web forms in Sun Solaris Client PC. If yes what is the way, either do we need to use the Netscape Navigator browser or some thing else to invoke the same.
    Thanks in advance.
    Regards,
    S.Karthick

    Please post Forms questions on the Forms discussion board.
    You'll need a browser (netscape will do) and a JVM (you can use Sun's Java plug-in).
    More info on how to setup this configuration is here:
    http://otn.oracle.com/products/forms/pdf/forms_jdk141.pdf

  • Solaris-Client/Server on same machine

    Was wondering if it was a problem to have the client and server on the same solaris box.When accessed by another client machine the forms are fine, but when accessed from the same machine (client), forms don't seem to function as programmed, tab pages etc..
    Any info would help.
    Thanks

    Was wondering if it was a problem to have the client and server on the same solaris box.When accessed by another client machine the forms are fine, but when accessed from the same machine (client), forms don't seem to function as programmed, tab pages etc..
    Any info would help.
    Thanks

  • Boot server for solaris clients

    Can any one give me the steps to configure a temporary boot server .. so that i can boot one of my failing server which does not have cdrom .
    I do not want to configure full fledge jumpstart box .. i need it just for recovery purpose. And i want to set it up in one of my other servers .. which is running several solaris zones.

    Setting up a "full" jumpstart server is quite easy. You just don't have to make lots of customizations to enable non-interactive installs.
    Run the setup_install_server on the media to copy the data to the server. If using CD sets, go through each of the other disks and run the update_install_server scripts. Then run add_install_client in the destination Tool directory to set up all the config files for the client.
    (It's possible to skip the first step and do the client setup from the DVD directly, but this is usually simpler).
    Darren

  • Network install fron x86 solaris server to x86 solaris client ?

    My setup is:
    install server OS: Solaris 10, i86pc .
    The install server is also boot server using tftpboot.
    The dhpc server is configured according to the instructions which are
    given when adding an install client in Solaris 10.
    The client can communicate with the install and boot server but fails
    to load the boot image. The snoop output is
    Using device /dev/iprb0 (promiscuous mode)
    cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
    cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
    cdm3 -> cdm2 UDP D=2070 S=39122 LEN=22
    cdm2 -> cdm3 TFTP Error: not defined
    cdm2 -> cdm3 TFTP Read "nbp.cdm2" (octet)
    cdm3 -> cdm2 UDP D=2071 S=39123 LEN=23
    cdm2 -> cdm3 TFTP Ack block 0
    cdm3 -> cdm2 TFTP Data block 1 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 1
    cdm3 -> cdm2 TFTP Data block 2 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 2
    cdm3 -> cdm2 TFTP Data block 3 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 3
    cdm3 -> cdm2 TFTP Data block 4 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 4
    cdm3 -> cdm2 TFTP Data block 5 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 5
    cdm3 -> cdm2 TFTP Data block 6 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 6
    cdm3 -> cdm2 TFTP Data block 7 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 7
    cdm3 -> cdm2 TFTP Data block 8 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 8
    cdm3 -> cdm2 TFTP Data block 9 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 9
    cdm3 -> cdm2 TFTP Data block 10 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 10
    cdm3 -> cdm2 TFTP Data block 11 (1456 bytes)
    cdm2 -> cdm3 TFTP Ack block 11
    cdm3 -> cdm2 TFTP Data block 12 (172 bytes) (last block)
    cdm2 -> cdm3 TFTP Ack block 12
    cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
    cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
    cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
    cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
    cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
    cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
    cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
    cdm2 -> BROADCAST DHCP/BOOTP DHCPDISCOVER
    cdm3 -> cdm2 ICMP Echo request (ID: 48130 Sequence number: 0)
    cdm3 -> cdm2 DHCP/BOOTP DHCPOFFER
    And then fails: i.e. it seems not to find the boot image.
    Any suggestions???
    Lydia

    I must have been too late previously. I got a whole host of output now.
    The boot clearly tries to get underway, but configs fail, such as the real
    boot file. I followed the instructions in the manual to setup the
    dhcp server but must be missing something.
    The output on the client is:
    PXE BIOS stack - 8cc006e8
    NBP ends at d108.
    Buffer starts at d110.
    Reserved memory starts at 8cc00.
    Buffer size is 522992 bytes.
    Checking !PXE structure at 9cf60070.
    UNDIROMID c08000020, BaseROMID 0
    StatusCallout 0
    SegDesCnt 7, FirstSelector 0
    Stack selector 8cc0, base 8cc00, size 800
    UNDIDate slelector 96d9, base 96d90, size 61d0
    UNDICode selector 9cf6 base 9cf690, size 2c40
    UNDICodeWrite selector 9cf6, bse 9cf690, size 2c40
    BC_Daate selector 8d40, base 8d400, size 3950
    BC_Code slecttor 90d5, base 90d50, size 603e
    BC_CodeWrite selector 90d5, bse 90d50, size 603e
    Valid !PXE passed in by BIOS.
    PXE is present
    Calling PXENV_UNDI_GET_NIC_TYPE
    Network boot dievice is PCI device 308, vendor ID 8060, device ID 1013
    get_cached_info discover succeeded:
    client IP: 0:0:0:0
    your IP: 0:0:0:0
    next server IP: 0:0:0:0
    relay agent IP: 0:0:0:0
    client MAC addr: 0:30:48:71:1c:44
    server name:
    boot file:
    get_cache_info ack succeeded:
    client IP: 0:0:0:0
    your IP: 129.234.194.12
    nextt server IP: 129.234.194.13
    relay agent IP: 0:0:0:0
    client MAC addr: 0:30:48:71:1c:44
    server name:
    boot file: nbp.cdm2
    Network bootstrap program server was 129.234.194.13
    Network bootstrap program file was nbp.cdm2.
    get_cached_info reply succeeded:
    client IP: 0:0:0:0
    Your IP: 129.234.194.12
    next server IP: 129.234.194:13
    relay agent IP: 0:0:0:0
    client MAC addr: 0:30:48:71:1c:44
    server name:
    boot file: nbp.cdm2
    Calling PXENV_UNDI_GET_INFORMATION
    client MAC address is 0:30:48:71:1c:44.
    PXENV_UDP_OPEN succeeded
    Broadcasting DHCPDISCOVER for class ID SUNW.i86pc.
    PXENV_UDP_WRITE succeeded
    PXEENV_UDP_READ failed, reet = 1, status =1
    PXENV_UDP_READ failed, ret = 1, status = 1
    When I checked access dates on files
    in /tftpboot on the server I found that
    nbp.cdm2 (the link) and nbp.I86PC.Solaris_10-1
    had access times = time of boot attempt of client, but that
    inetboot.I86PC.Solaris_10-1 had not been touched.
    in the dhcp configuration there is no reference to inetboot.I86PC.Solaris_10-1 .
    Any further ideas ?
    Lydia

  • JDBC 2.0 OCI on Tru64 with a Solaris client?

    We are considering running 8.1.7 on a Compaq True64 machine as our database server. We will be running some type of app server on a Sun Solaris machine that will use EJB's to connect to the database server. We would like to be using the OCI JDBC drivers as opposed to the thin-client drivers.
    Is the configuration that I've presented here feasible, and if so, has anyone here had any good/bad experiences that they could relate? I ask because we recently discovered that we could not use a JDBC 2.0 compliant OCI driver under Linux and we have had trouble finding documentation on Oracle for True64.
    Any comments/feedback would be appreciated. Thanks.
    Jansen McNay
    DBA, Digital Media On Demand
    null

    If you want to use JDBC2.0, be sure to execute "usejdbc2.bat" in $DB2DIR$/java12 once.

  • Linux and Solaris Clients with password policy using LDAP

    Anybody managed to get Linux (RHEL) and Solaris 9 Client authenticate against Sun Directory Server 5.2p4 using the same password policy?
    For me it looks like Linux needs attribute shadowlastchanged set to display proper Warnings, that the password will expire/needs to be changed now. On the other hand Solaris (using pam_ldap) never writes this attribute, because it's using the password policy attribute pwdchangedtime.
    Hints very wellcome!
    Can anybody confirm Solaris9 pam_unix still sets this shadow* attributes correct on any password change executed by a user?

    Hi Jeremy,
    here the answers to your questions:
    >My question is which system takes precedence over the password policy?
    Unfortunately there is no policy verification between the portal and your Sun One LDAP. So if you reset the password from the portal then only the portal password policies can be checked.
    >  If I wanted to do password resets from the Portal, does the portal then store only the password in its database?
    No, the password will be stored in the LDAP, but only if it also corresponds with the LDAP policies. If not, then you will get an error, but you will not see the real LDAP exception.
    > Also what would then happen if you tried to reset the password from the LDAP?
    The password in the LDAP does not have to fit to the Portal password policies. When you log in, the portal will only check if the password you tipped in is the new one in LDAP and will not check any policies.
    Hope this brings some light in,
    Robert

  • Solaris nis client can't connect to Windows 2008 NIS Server across subnets

    I have been using Microsoft Windows Server for NIS for years to centralize some accounts accessing Solaris and Linux OS.
    Windows 2003 R2 Indentity Management for UNIX version of Server for NIS was last working version with Solairs.
    After upgrading Domain to Windows 2008 all Solaris clients that are on different subnets fail to bind and connect to NIS servers now.
    These servers already were setup using ypinit -c to manually add the NIS servers to connect to and prior to Windows 2008 this worked.
    Now no Solaris nis clients on different subnets (no firewall between) can connect , but other Unix/Linux OS connect fine.
    Is this a known issue and can we get a resolution as it seems only Solaris is affected?

    Hi Mid.Hudson-IT,
    Before we begin ,we should ensure we have configured the printer server correctly .
    Here is a link for reference of configuring the printer server .
    Print server role: Configuring a print server
    https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
    "I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
    From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
    If we can ping the print server from the client,we can ensure the connection to the printer server is good .
    Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
    If we cannot ping the print server ,we should troubleshoot the network issue firstly.
    We also can check the event viewer for more information to troubleshoot this issue .
    Best regards

  • Solaris 9 NFS clients and Mac OS X 10.3.8 NFS Server issues

    I have a situation where I'm using a Mac OS X Server machine as my file server for heterogeneous mix of clients, Solaris 9 being one of them. The NFS server portion of Mac OS X seems to have some quirks. I made the move to a Mac OS X server from a combination of Linux and Solaris because it was touted as a good multi-platform server solution, but my NFS woes are souring my opinion of it
    I haven't been able to nail down the exact cause, but it seems that Sun's Gnome Destop 2.0 has problems starting up. The 'gconfd-2' process starts and never finishes what it's doing. I'm suspecting a problem with creating a lock file in the user's NFS mounted home directory. My workaround was to disable the Gnome Desktop 2.0 option, but it isn't very pleasant because many of my users liked it.
    Another strange issue that plagues the Solaris 9 and Linux (Fedora 2) users is that Mozilla, which is the primary email client for my users, complains that it "Could not initialize the browser's security component." It goes on to suggest that there may be a problem with read / write access with the user's profile directory or that there's no more room. Googling didn't turn up much about this problem, but the home directory share is nowhere near full and the permissions are such that eveyone can read and write to their own profile directory just fine. I've been able to work around this problem on Linux by removing the user's 'cert8.db' and 'key3.db' files before they run Mozilla, but this technique is failing to work on the Solaris 9 clients.
    All these problems seem to involve some strange file access issue, and the Linux and Solaris clients had no problems when I was using a Solaris box for home directory sharing via NFS, so it definitely seems like a problem with Mac OS X's NFS implementation.
    If anyone has come across this type of issue and has some information about a fix or a better workaround, I would love to hear from you. Thanks in advance!

    I just figured out today that the Gnome Desktop 2.0 problem is due to some part of Gnome not liking really long home directory paths. Mac OS X by default dictates that home directories be of the form /Network/Servers/(fqdn of file server)/Volumes/(volume name)(home directory share path), for example, /Network/Servers/xxx.myschool.edu/Volumes/Homes/userx. I haven't figured out what in Gnome doesn't like it, but it appears to be the gconf mechanism.
    The Mozilla strangeness still is happening though.
    Quote: schwenk wrote on Fri, 15 April 2005 11:09
    I haven't been able to nail down the exact cause, but it seems that Sun's Gnome Destop 2.0 has problems starting up. The 'gconfd-2' process starts and never finishes what it's doing. I'm suspecting a problem with creating a lock file in the user's NFS mounted home directory. My workaround was to disable the Gnome Desktop 2.0 option, but it isn't very pleasant because many of my users liked it.

  • Solaris 10 LDAP Client to 389 DS(Linux)

    Hey guys,
    I had this working in Solaris 11 but I have to port back to Solaris 10 to run SunOS 4 binaries. Here goes, I can su over to the accounts in the LDAP, it resolves names and groups to files. DNS and NTP are functioning. I cannot log -in via ssh or su <username>. I can log in or su with both methods with local accounts(non-LDAP).
    When I - su Username the system responds prompting for password then returns su: Uknown id: Username
    When I ssh [email protected] it prompts me three times for a password which it never accepts as valid.
    Here is my pam.conf file -
    #ident "@(#)pam.conf 1.31 07/12/07 SMI"
    # Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # PAM configuration
    # Unless explicitly defined, all services use the modules
    # defined in the "other" section.
    # Modules are defined with relative pathnames, i.e., they are
    # relative to /usr/lib/security/$ISA. Absolute path names, as
    # present in this file in previous releases are still acceptable.
    # Authentication management
    # login service (explicit because of pam_dial_auth)
    login auth requisite pam_authtok_get.so.1
    login auth required pam_dhkeys.so.1
    login auth required pam_unix_cred.so.1
    login auth sufficient pam_unix_auth.so.1
    login auth required pam_dial_auth.so.1
    login   auth required           pam_ldap.so.1
    # rlogin service (explicit because of pam_rhost_auth)
    rlogin auth sufficient pam_rhosts_auth.so.1
    rlogin auth requisite pam_authtok_get.so.1
    rlogin auth required pam_dhkeys.so.1
    rlogin auth required pam_unix_cred.so.1
    rlogin auth required pam_unix_auth.so.1
    # Kerberized rlogin service
    krlogin auth required pam_unix_cred.so.1
    krlogin auth required pam_krb5.so.1
    # rsh service (explicit because of pam_rhost_auth,
    # and pam_unix_auth for meaningful pam_setcred)
    rsh auth sufficient pam_rhosts_auth.so.1
    rsh auth required pam_unix_cred.so.1
    # Kerberized rsh service
    krsh auth required pam_unix_cred.so.1
    krsh auth required pam_krb5.so.1
    # Kerberized telnet service
    ktelnet auth required pam_unix_cred.so.1
    ktelnet auth required pam_krb5.so.1
    # PPP service (explicit because of pam_dial_auth)
    ppp auth requisite pam_authtok_get.so.1
    ppp auth required pam_dhkeys.so.1
    ppp auth required pam_unix_cred.so.1
    ppp auth required pam_unix_auth.so.1
    ppp auth required pam_dial_auth.so.1
    # Default definitions for Authentication management
    # Used when service name is not explicitly mentioned for authentication
    other auth requisite pam_authtok_get.so.1
    other auth required pam_dhkeys.so.1
    other auth required pam_unix_cred.so.1
    other auth sufficient pam_unix_auth.so.1
    other   auth required           pam_ldap.so.1
    # passwd command (explicit because of a different authentication module)
    passwd auth sufficient pam_passwd_auth.so.1
    passwd  auth required           pam_ldap.so.1
    # cron service (explicit because of non-usage of pam_roles.so.1)
    cron account required pam_unix_account.so.1
    # Default definition for Account management
    # Used when service name is not explicitly mentioned for account management
    other   account sufficient      pam_ldap.so.1
    other account requisite pam_roles.so.1
    other account required pam_unix_account.so.1
    # Default definition for Session management
    # Used when service name is not explicitly mentioned for session management
    other session required pam_unix_session.so.1
    # Default definition for Password management
    # Used when service name is not explicitly mentioned for password management
    other password required pam_dhkeys.so.1
    other password requisite pam_authtok_get.so.1
    other password requisite pam_authtok_check.so.1
    other password required pam_authtok_store.so.1
    # Support for Kerberos V5 authentication and example configurations can
    # be found in the pam_krb5(5) man page under the "EXAMPLES" section.
    Any ideas? So close but missing something as when I go to log in via ssh it prompts me for password 3 times then tosses me. Yes password and account are OK. If I ssh from a Linux server authenticating to the LDAP it works just fine. Any help is appreciated.
    Thanks,
    Ted

    CN,
    I have not modified the schema yet. I have updated pam.conf and while evaluating /var/adm/messages on the Solaris Client I only get output when I enter a known bad password, if I enter the correct password there is nothing in that log. Log in and su results remain the same. the slapd log does show the attempts and does not appear to show any errors that I can tell. I'll keep working it, here is the pam.conf I switched too after further evaluation -
    # more /etc/pam.conf
    #ident "@(#)pam.conf 1.31 07/12/07 SMI"
    # Copyright 2007 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # PAM configuration
    # Unless explicitly defined, all services use the modules
    # defined in the "other" section.
    # Modules are defined with relative pathnames, i.e., they are
    # relative to /usr/lib/security/$ISA. Absolute path names, as
    # present in this file in previous releases are still acceptable.
    # Authentication management
    # login service (explicit because of pam_dial_auth)
    login auth requisite pam_authtok_get.so.1
    login auth required pam_dhkeys.so.1
    login auth required pam_unix_cred.so.1
    login auth required pam_dial_auth.so.1
    login auth binding pam_unix_auth.so.1 server_policy
    login auth required pam_ldap.so.1
    # rlogin service (explicit because of pam_rhost_auth)
    rlogin auth sufficient pam_rhosts_auth.so.1
    rlogin auth requisite pam_authtok_get.so.1
    rlogin auth required pam_dhkeys.so.1
    rlogin auth required pam_unix_cred.so.1
    rlogin auth binding pam_unix_auth.so.1 server_policy
    rlogin auth required pam_ldap.so.1
    # Kerberized rlogin service
    krlogin auth required pam_unix_cred.so.1
    krlogin auth required pam_krb5.so.1
    # rsh service (explicit because of pam_rhost_auth,
    # and pam_unix_auth for meaningful pam_setcred)
    rsh auth sufficient pam_rhosts_auth.so.1
    rsh auth required pam_unix_cred.so.1
    rsh auth binding pam_unix_auth.so.1 server_policy
    rsh auth required pam_ldap.so.1
    # Kerberized rsh service
    krsh auth required pam_unix_cred.so.1
    krsh auth required pam_krb5.so.1
    # Kerberized telnet service
    ktelnet auth required pam_unix_cred.so.1
    ktelnet auth required pam_krb5.so.1
    # PPP service (explicit because of pam_dial_auth)
    ppp auth requisite pam_authtok_get.so.1
    ppp auth required pam_dhkeys.so.1
    ppp auth required pam_dial_auth.so.1
    ppp auth binding pam_unix_auth.so.1 server_policy
    ppp auth required pam_ldap.so.1
    # Default definitions for Authentication management
    # Used when service name is not explicitly mentioned for authentication
    other auth requisite pam_authtok_get.so.1
    other auth required pam_dhkeys.so.1
    other auth required pam_unix_cred.so.1
    other auth binding pam_unix_auth.so.1 server_policy
    other auth required pam_ldap.so.1
    # passwd command (explicit because of a different authentication module)
    passwd auth binding pam_passwd_auth.so.1 server_policy
    passwd auth required pam_ldap.so.1
    # cron service (explicit because of non-usage of pam_roles.so.1)
    cron account required pam_unix_account.so.1
    # Default definition for Account management
    # Used when service name is not explicitly mentioned for account management
    other account requisite pam_roles.so.1
    other account binding pam_unix_account.so.1 server_policy
    other account required pam_ldap.so.1
    # Default definition for Session management
    # Used when service name is not explicitly mentioned for session management
    other session required pam_unix_session.so.1
    # Default definition for Password management
    # Used when service name is not explicitly mentioned for password management
    other password required pam_dhkeys.so.1
    other password requisite pam_authtok_get.so.1
    other password requisite pam_authtok_check.so.1 force_check
    other password required pam_authtok_store.so.1 server_policy
    # Support for Kerberos V5 authentication and example configurations can
    # be found in the pam_krb5(5) man page under the "EXAMPLES" section.
    ppp auth required pam_unix_cred.so.1
    ppp auth required pam_unix_auth.so.1
    I did create a .ldif file for a profile. Output seems similar to what I entered in the manual ldapclient command. Reading up more on that now and the schema updates you recommended. I wanted to make sure I sent you the updated pam.conf though as this seems to match those found online in style for pre-Solaris 11. The first copy was what I transferred from a working Solaris 11 server I had running here.
    Thanks,
    Ted

  • Solaris 10 NFS client and readdir

    I have a Solaris 10 u5 client that mounts a directory using NFS from a Mac OS X server. The mount works fine and programs and tools such as /bin/ls, etc work ok. However, several programs that I have that use the readdir (or readdir_r) library calls never return lists of files from this NFS mounted directory (point these programs at a ufs/zfs file system and all works fine). I created a simple test using readdir and it happens in that as well. The only thing that it will find/list is the "." and the ".." directories for anything in the NFS mounted name space.
    I found a reference to the nfs:nfs3_shrinkreaddir and the nfs:nfs_shrinkreaddir solaris tunable parameters and placed them both in the /etc/system file and rebooted, but it did not change the behavior. I also tried setting the nfs:nfs_disable_rddir_cache=1 and related entities to no avail.
    I also noticed that tar was dumping core reading this directory, but have found a patch for tar to fix this. It did not include any guidance on nfs parameters for Mac OS X or similar NFS v3 servers.
    Is there some set of NFS settings that I can make that will enable this Solaris client to mount the file system and be able to actually read the directories and files?

    I believe I have found my problem. Turns out that it appears to be only remotely related to NFS. The application I have is built for 32 bits and the O/S is an i386/x64 system. Apparently, readdir fails when it gets an "nfs" inode when it is built in 32 bit mode - works fine when compiled with -m64. So now I need to track down some x64 builds of the failing packages.

  • Veritas Netbackup Client 6 for Solaris 10

    Hi
    Can anyone tell me where I can download Veritas Netbackup client for Solaris 10. We had the netbackup client for solaris 9 running but then we did a clean install of Solaris 10.
    The netbackup server is running on an AIX server and I want to push the solaris client from there. We have separate license for all our clients running the netbackup agent but the netbackup server does not have the latest solaris 10 client. The AIX server do not have internet access, so I want to download the solaris 10 netback agent and put on the netbackup server.
    Need to know the URL where I can download the netbackup agent for Solaris 10.
    Many Thanks
    Pioneer

    Hi mcbrune1
    I've check on the services in the client and all 4 services were up and running. Than I realized that this client was hardened a few weeks back. So I checked on the /etc/hosts.allow file and added an entry to allow the Master server to communicate using bpcd.
    Now the Master server is able to see the client and everything seems to be working. Thanks for your help.
    Cheers

  • NFS latency when Solaris 10 client mounts Linux NFS server(EMC NAS)

    Hello,
    One of our developers discovered a problem that for simplicity we call "latency". We have several 5.10 clients that we see the exact same symptoms on when NFS mounting our Celerra. The NAS is running a Linux variant "2.4.9-34.5406.EMC", but before you all jump on the "it's EMC's problem" bandwagon, let me explain. We set up an automated process (Perl) that watches an exported folder for the appearance of a request file (rand.req). When the request file comes in we rename the request file to (rand.sav) and then return a "report" named (rand.res). Very elegent I thought, and it runs at near lightspeed when only Linux NFS clients mount the share and create, monitor, delete, etc any files. In fact there is zero recorded latency from the time the report file appears and when the client detects it. But for all our Solaris 10 clients, they create the request file just fine, and the Perl process running on the Linux box sees the file instantaneously and returns the report, but it takes the Solaris client anywhere from 5 to up to 50 seconds before it see's any change in status for any files the Linux box manipulates. I've tried every possible combination of mount -o options there are including noac, rsize and wsize variants, vers=2, proto=udp, actimeo=0, etc, etc, etc. Nothing seems to be the magic bullet. nfsstat -c shows nothing out of the ordinary. There are no retransmits or dropepd packets anywhere in between, no firewall loads, no connectivity delays whatsoever. I'm completely out of ideas. Any ideas or clues would be greatly appreciated!
    thanks
    Dave

    No specific recommendations. But maybe you can watch the cable and get more information.
    Set up a case where the file has been created, then have the client check and snoop the cable at the same time. Does the client actually issue a directory check (or is it just displaying cached information)? Does the response contain the new file?
    Something to test anyway...
    Darren

  • Problems logging in from Solaris 8 client

    I was given a tarball, from Sun, with instructions on how to install and configure iDS 5.1 to work with Solaris clients.
    I was able to bring over all of my nis maps successfully and my automounts work on the client machine from the NFS server so I know there's communication going on through LDAP. The one thing that doesn't work is when I try and login to the client machine as a valid user. It prompts for the password but rejects the login. I can log in as root to the client and su to any valid username in the LDAP directory and it's fine. I show the correct id and home directory. It's only when I try and enter a password that I have the problem.
    Both the ldap server and client are Solaris 8 2/02 HW release with patches through May. The machines are on a private network so there's no outside interference.
    I've double checked the encryption setting, and the error logs don't show anything that tips me off. Any ideas?
    Thanks

    I also tried to remove the client and re-entered it. Also I tried to jumpstart another client at the same time and that worked. But however this particular client does not boot.
    Looking at some sites, I found that env variables such as mfg-switch?, diag-device? and boot-device needs to be set right values. I verified them as well.
    For eg:
    boot-device is set to "disk "
    diag-device? is set to false
    However I do not have mfg-switch? env variable. But this not available in other clients which boot properly. So I don't think these are causing problems.
    Another point was that it could be due to network issues. I booted the client, opened a telnet session from JS server to the client and ran snoop on JS server. The connectivity was ok and snoop showed the same MAC address as configured in /etc/ethers.
    My only guess is if something is wrong with the port configuration on the LAN switch. I believe JS works in Layer 2 level.
    Can you please let me know if you have come across with problems due to network port configuration in LAN switch.

Maybe you are looking for