Network install from solaris 10 x86 server to x86 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 can't tell exactly what's wrong, since you attached only
snoop log.
But since you're using DHCP, I guess you are trying to
do PXE boot to install. When you use PXE boot, you need
to configure some vendor options (like SrootIP4, SrootNM
etc) and also create macros with dhcpmgr.
there is documentation at
http:docs.sun.com
so check the documentation to see what is missing.
If you've already done these, check NFS configuration
if all directory are correctly shared.

Similar Messages

  • Networking changes between Solaris 10 x86 10/08 (u6) and previous versions?

    Solaris Community:
    We have a J2SE CORBA-based application (that uses the default Sun ORB) that has run without problems on Solaris 8, 9, and 10 on both SPARC and, more recently, X86 platforms. Upgrading our client side machine (X4100 M2 Opteron platform) from Solaris 10 x86 5/08 (u5) to Solaris 10 x86 10/08 (u6) has resulted in threading or socket contention issues that we have not experienced previously. Using Live Upgrade, we can quickly go back to the u5 install on the client machine .... and the problems go away .... going back to u6, however, and the problems begin to show almost immediately. Our Java code base is identical as is the version of the JDK (1.5.0_16), so it would appear that there must be an underlying change to socket, networking, or threading behavior between these two versions of Solaris.
    Thus far, I've not been unable to find details of changes either in the networking support or the threading model that might explain this .... or course, I don't have great expertise in these areas.
    I've tried to use 'ndd /dev/tcp SOME_PARAMETER' for all of the /dev/tcp parameters returned by 'ndd /dev/tcp \?' to try to see if there are underlying changes in the /dev/tcp parameters .... but have not found any differences between Solaris 10 u5 and u6.
    Can anyone point me to resources that would discuss changes between Solaris 10 u5 or u6 that might explain the problems that we've encountered? Or, alternatively, other system parameters that I could check that might explain changes in either TCP socket or threading behavior?
    Thanks for your input,
    John

    I have a vague memory of someone reporting something similar which turned out to be due to a solaris feature called tcp_fusion.
    To check whether thats your problem or not try the following.
    Add following line in the /etc/system file.
    set ip:do_tcp_fusion = 0
    Once the /etc/system file is updated, it will be necessary to restart the system before the workaround will take effect.

  • Install network card on solaris 8 x86 10/1

    Hi
    how can I install my netwoek card on solaris 8 x86
    Thank a lot

    In the same way you install any other card. Plug the card in
    the slot., and install the appropriate solaris driver for that
    network card. May be you want to detail the problem, if this
    is not you are looking for.
    Thx
    Tushar Patel.

  • Problem jumpstarting a Solaris 9 SPARC from Solaris 10 x86

    Hi all,
    I'm going to install a couple of servers using Jumpstart, but I've run
    into a problem so I'm kinda in panic.
    This is the net boot:
    Executing last command: boot net - install
    Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
    Timeout waiting for ARP/RARP packet
    29200 panic - boot: Could not mount filesystem.
    Program terminated
    ok
    I've setup the jumpstart server on my x86 PC, which is Solaris 10 final
    with JET 3.7.3. Since I'm jumpstarting Solaris 9 onto a SPARC machine, I
    had to do copy_solaris_media over NFS, since I can't mount the SPARC
    ISO-CD1 on my x86. The install server seems to be OK, at least it didn't
    complain during setup.
    The log entry from sniffing the JS server:
    3266 1:15:25.48103 aaa -> xxx WHO C port=33345
    3267 1:15:25.48427 aaa -> xxx WHO C port=33345
    3268 1:15:25.48636 aaa -> xxx WHO C port=33345
    3269 1:15:25.48748 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
    3270 1:15:25.49044 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
    3271 1:15:25.49283 aaa -> xxx SYSLOG C port=32775 BAD.FMT:
    3272 1:15:25.49394 aaa -> xxx PORTMAP R GETPORT port=32775
    3273 1:15:25.49541 aaa -> xxx PORTMAP R GETPORT port=32775
    3274 1:15:25.49673 aaa -> xxx PORTMAP R GETPORT port=32775
    3275 1:15:25.49867 aaa -> xxx PORTMAP R GETPORT port=32775
    /etc/bootparams:
    xxx root=aaa:/opt/install/media/Solaris_9/Solaris_9/Tools/Boot
    install=192.168.4.5:/opt/install/media/Solaris_9 boottype=:in
    sysid_config=192.168.4.5:/opt/jet/Clients/xxx
    install_config=192.168.4.5:/opt/jet rootopts=:rsize
    32768
    term=:vt100
    Any idea what could be wrong? It stops at 29200, wheres Solaris 10 runs
    further up to 38000 something.
    Jumpstarting the Solaris 10 onto the same SPARC works perfectly, using
    the exact same configuration files.
    Thanks

    Hi all,
    I managed to solve the problem.
    This is very weird! can someone explain why this happens?
    Output for working Solaris 10 boot:
    Executing last command: boot net -v
    Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
    38600 Using RARP/BOOTPARAMS...
    Internet address is: 192.168.4.6
    hostname: xxx
    Requesting Ethernet address for: 192.168.4.5
    Found 192.168.4.5 @ 0:0:86:1f:f7:92
    root server: aaa (192.168.4.5)
    root directory: /opt/install/media/Solaris_10/Solaris_10/Tools/Boot
    Size: 0x704c8+0x1b8d2+0x2e1ba Bytes
    Output for non-working Solaris 9 boot:
    Executing last command: boot net -v
    Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v
    Timeout waiting for ARP/RARP packet
    29200 Using RARP/BOOTPARAMS...
    Internet address is: 192.168.4.6
    hostname: xxx
    Found 192.168.4.5 @ 0:0:86:1f:f7:92
    root server: aaa (192.168.4.5)
    root directory: /opt/install/media/Solaris_9/Solaris_9/Tools/Boot
    panic - boot: Could not mount filesystem.
    Program terminated
    ok
    I then replaced /tftpboot/inetboot.SUN4U.Solaris_9-1 with /tftpboot/inetboot.SUN4U.Solaris_10-1 from the Solaris 10 tree, renamed /tftpboot/inetboot.SUN4U.Solaris_10-1 to /tftpboot/inetboot.SUN4U.Solaris_9-1
    Voila!
    Now works.
    inetboot.SUN4U.Solaris_9-1 was not corrupt (must be some internal bootimage bug related to Netra-T1?).
    Old bootimage: "inetboot.SUN4U.Solaris_9-1", 152376 bytes, "sum" 3662 and 298.
    New bootimage: "inetboot.SUN4U.Solaris_9-1" (Sol 10 image), 214880 bytes, "sum" 53512 and 420.
    By the way I was using latest Solaris 9/04, u7

  • Intel network interface with Solaris 10 x86

    Hi,
    I have been Googling all evening to try and find a solution to this, but here is the problem:
    I have a PC built around an Asus P4C800-E system board, and I have Solaris 10 x86 01/2006 installed. I would like to get the Ethernet interface (Intel adaptor, running on a CSA bus) up and running - but for some reason I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
    I know the NIC is working, and have tried it under other OSes (including Linux).
    Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
    Is there a way I can convince the driver to bind to pci8086,1019 instead of pci1043,80f7?
    Any assistance would be greatly appreciated.
    Joovilhar.

    <table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Joovilhar wrote on Wed, 08 March 2006 02:14</b></td></tr><tr><td class="quote">
    I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
    </td></tr></table>
    Is 1043,80f7 the device's pci subsystem vendor and subsystem device id?
    And 8086,1019 is the normal vendor/device id?
    In this case everything would work as expected.
    What is listed by "/usr/X11/bin/scanpci -v" for the ethernet controller?
    <table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
    I know the NIC is working, and have tried it under other OSes (including Linux).
    Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
    </td></tr></table>
    Try to boot the kernel with various settings of the "acpi-user-options" variable,
    to disable / enable ACPI. In previous Solaris x86 releases, when
    something went wrong configuring an interrupt vector for a nic device,
    the typical end result is a nic that is unable to receive incomming
    packets. Maybe your Asus P4C800-E is still problematic with ACPI, with
    S10 x86 1/2006, and needs the acpi-user-options workaround.
    http://blogs.sun.com/roller/page/danasblog?anchor=configurin g_solaris_acpi_at_boot
    To change the "acpi-user-options" variable, edit the grub boot command
    line and edit the "multiboot" line, e.g. append "-Bacpi-user-options=0x2".

  • Network install target says RARP timeout, server says reply sent

    I had an existing Solaris jumpstart install server that I initially tried setting up for DHCP, and then after much failure tried resetting it to used fixed IP on a different subnet.
    I've done add_install_client (without the -d dhcp option) and made sure the correct entries were in /etc/ethers and /etc/hosts
    When I do boot net - install from the target machine, I get:
    ok boot net - install
    Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
    Timeout waiting for ARP/RARP packet
    Timeout waiting for ARP/RARP packet
    I have /usr/sbin/in.rarpd -d -a & running in a window and it shows me:
    /usr/sbin/in.rarpd/usr/sbin/in.rarpd:[3] RARP_REQUEST for 0:3:ba:35:cf:f8:[3
    ] RARP_REQUEST for 0:3:ba:35:cf:f8
    /usr/sbin/in.rarpd:[3] trying physical netnum 10.120.1.0 mask ffffff00
    /usr/sbin/in.rarpd:[3] good lookup, maps to 10.120.1.210
    /usr/sbin/in.rarpd:[3] trying physical netnum 10.120.1.0 mask ffffff00
    /usr/sbin/in.rarpd:[3] good lookup, maps to 10.120.1.210
    /usr/sbin/in.rarpd/usr/sbin/in.rarpd:[3] :[3] RARP_REQUEST for 0:3:ba:35:cf:f8
    RARP_REQUEST for 0:3:ba:35:cf:f8
    snoop -d eri0 | grep -i arp shows me
    OLD-BROADCAST -> (broadcast) RARP C Who is 0:3:ba:35:cf:f8 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    10.120.1.1 -> (broadcast) ARP C Who is 10.120.1.10, 10.120.1.10 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    OLD-BROADCAST -> (broadcast) RARP C Who is 0:3:ba:35:cf:f8 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    ni-sparc -> ems-6 RARP R 0:3:ba:35:cf:f8 is 10.120.1.210, ems-6
    ni-sparc -> ems-6 RARP R 0:3:ba:35:cf:f8 is 10.120.1.210, ems-6
    So according to the server feedback, it looks like the RARP lookup is working, but the client isn't getting the response.
    Any thoughts?

    msully wrote:
    I had an existing Solaris jumpstart install server that I initially tried setting up for DHCP, and then after much failure tried resetting it to used fixed IP on a different subnet.
    I've done add_install_client (without the -d dhcp option) and made sure the correct entries were in /etc/ethers and /etc/hosts
    When I do boot net - install from the target machine, I get:
    ok boot net - install
    Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: - install
    Timeout waiting for ARP/RARP packet
    Timeout waiting for ARP/RARP packetIf you leave this running for a while, do you continually get more lines, or does it stop at a small number (like 5 or so)?
    >
    I have /usr/sbin/in.rarpd -d -a & running in a window and it shows me:
    /usr/sbin/in.rarpd/usr/sbin/in.rarpd:[3] RARP_REQUEST for 0:3:ba:35:cf:f8:[3
    ] RARP_REQUEST for 0:3:ba:35:cf:f8
    /usr/sbin/in.rarpd:[3] trying physical netnum 10.120.1.0 mask ffffff00
    /usr/sbin/in.rarpd:[3] good lookup, maps to 10.120.1.210
    /usr/sbin/in.rarpd:[3] trying physical netnum 10.120.1.0 mask ffffff00
    /usr/sbin/in.rarpd:[3] good lookup, maps to 10.120.1.210
    /usr/sbin/in.rarpd/usr/sbin/in.rarpd:[3] :[3] RARP_REQUEST for 0:3:ba:35:cf:f8
    RARP_REQUEST for 0:3:ba:35:cf:f8
    snoop -d eri0 | grep -i arp shows me
    OLD-BROADCAST -> (broadcast) RARP C Who is 0:3:ba:35:cf:f8 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    10.120.1.1 -> (broadcast) ARP C Who is 10.120.1.10, 10.120.1.10 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    OLD-BROADCAST -> (broadcast) RARP C Who is 0:3:ba:35:cf:f8 ?
    10.120.1.74 -> (broadcast) ARP C Who is 10.120.1.32, 10.120.1.32 ?
    ni-sparc -> ems-6 RARP R 0:3:ba:35:cf:f8 is 10.120.1.210, ems-6
    ni-sparc -> ems-6 RARP R 0:3:ba:35:cf:f8 is 10.120.1.210, ems-6Huh. I wonder why it took so long to respond? You got two RARP requests (and several random ARP requests) in the time it took to send the first reply.
    Do any more request/reply pairs come through on the network trace?
    So according to the server feedback, it looks like the RARP lookup is working, but the client isn't getting the response.If you get unlimited RARP request lines on the client, I'd agree. If they stop, then perhaps the system is hanging after the reply.
    Can you do a 'test-net' on the client OBP and see that it can view network traffic? Has the machine been booted with some OS to verify the interface is functional for receiving traffic?
    Darren

  • Issues w/ LiveUpgrade from Solaris 10 x86 06/06 to 08/07 w/ SVMmetadevices

    Hello all...
    I am trying to upgrade a system from Sol 10 x86 6/06 to 8/07. For this example, we'll assume the following:
    * The system has only 2 disks mirrored with SVM
    * There are 0 free slices/partitions
    * /, /usr, /var are separate slices/filesystems/mirrors
    * There are 6 metadbs on 50MB slices, three on each disk
    I run the following lucreate command (after having made sure that the appropriate packages and patches exist on the system):
    lucreate -c s10u2 -n s10u4 -m /:/dev/md/dsk/d110:ufs,mirror -m /:/dev/dsk/c0d1s0:detach,attach,preserve \
    -m /usr:/dev/md/dsk/d120:ufs,mirror -m /usr:/dev/dsk/c0d1s3:detach,attach,preserve \
    -m /var:/dev/md/dsk/d130:ufs,mirror -m /var:/dev/dsk/c0d1s4:detach,attach,preserveI can then run luupgrade and every indication leads me to believe that it worked. So, I activate the new BE and init 6 and attempt to boot to the new BE. The boot ends up failing citing that it cannot mount /usr. So, I can either reboot and lumount the filesystems or boot into failsafe mode and take a look at the vfstab. The /etc/vfstab looks fine with the new metadevices identified as the /, /usr, and /var filesystems. However, those metadevices are never initialized. When I look at /etc/lvm/md.cf on the source BE, those metadevices are initialized there. However, they are not initialized in the secondary BE.
    Am I missing something somewhere? Wondering why SVM does not appear to be updated on the secondary BE to add/initialize the new metadevices in the secondary BE.
    TIA,
    Rick

    Ok...update...
    I have found that there are bugs with LU where it relates to SVM mirrored /'s and what not. So, I modified my approach to the upgrade and "deconfigured" the /, /usr, and /var mirrors. I then executed the the procedure as described in the docs to create a new boot environment on the secondary disk. It worked!
    Great! With that done, I can then remove the old boot environment and remirror the /, /usr, and /var filesystems as it was prior to the LU procedure. Wrong answer! There were two problems, the first was fairly simple to overcome....
    Problem 1) When attempting to delete the old BE, I would get the following error:
    The boot environment <s10u2> contains the GRUB menu.
    Attempting to relocate the GRUB menu.
    /usr/sbin/ludelete: lulib_relocate_grub_slice: not found
    ERROR: Cannot relocate the GRUB menu in the boot environment <s10u2>.
    ERROR: Cannot delete the boot environment <s10u2>.
    Unable to delete boot environment.Through some Googling, I found that apparently, the Solaris 10 LiveUpgrade is attempting to use a function in /usr/lib/lu/lulib that only exists in OpenSolaris (whatever happened to backporting functionality?). Ok...easy enough. Backup the library and copy it over from an OpenSolaris box. Done...and it worked, but only led to problem #2...
    Problem 2) Now when I run ludelete on the old BE, I get the following error:
    The boot environment <s10u2> contains the GTRUB menu.
    Attempting to relocte the GRUB menu.
    ERROR: No suitable candidate slice for GRUB menu on boot disk: </dev/rdsk/c0d0p0>
    INFORMATION: You will need to create a new Live Upgrade boot environment on the boot disk to find a new candidate for the grub menu.
    ERROR: Cannot relocate the GRUB menu in boot environment <s10u2>.
    Unable to delete boot environment.I have attempted to manually move/install GRUB on the secondary disk and make it the active boot disk, all to no avail. ludelete returns the same error every time.
    Thoughts? Ideas?
    TIA,
    Rick

  • Fresh install of solaris 10 x86 hangs after 'Configuring devices'

    Hi All,
    I just received a new SuperMicro server with an LSI MegaRAID SAS 9261-8i controller. While trying to install Solaris 10 it hangs after "Configuring devices". I checked the LSI page and Solaris 10 is supported according to them. Any ideas how to proceed?
    Fairly new to Solaris on x86 hardware.
    The system has a Xeon X5690 processor in an Intel Workstation Board S5520SC motherboard. The motherboard documents claim that not disabling usb 2.0 can hang an install. I have disabled the usb 2.0 in the bios but the system still hangs. Booting it with the -kd and -kv options don't give much information.
    Any help is appreciated. I might be returning these machines if I can't get this worked out.
    Cheers,
    Steve
    Edited by: 967729 on Oct 25, 2012 3:51 PM

    See if you can add the verbose option "-v" to the kernel boot options. I think you can get to the GRUB menu off the Solaris 10 install disk. That should tell you what device is causing the hang, or at least the last device that worked.
    Also, can you try Solaris 11 and see if it gets past that point? A few years ago I has a similar issue with Solaris 10 on a Dell server. Solaris 11/OpenSolaris worked fine, though. IIRC I could work around the issue if I disabled the 2nd CPU - Solaris 10 had a problem bringing up the 2nd CPU on that Dell's CPU/MB config.

  • ODBC to DB2 from Solaris 10 X86 64

    I am trying to make a ODBC connection to a DB2 database on a AS400 via a datadirect ODBC driver. This is working.
    Now i am trying to use the hsdodbc driver to make a connection from the Oracle 10.2.0.4 64bit database on the Solaris 10 x86 64 bit.
    I modified the listener.ora.
    lsnrctl reload
    LSNRCTL for Solaris: Version 10.2.0.4.0 - Production on 21-APR-2009 15:24:14
    Copyright (c) 1991, 2007, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=srv020.emons.nl)(PORT=1521)))
    TNS-01201: Listener cannot find executable /oracle/oracle10/10.2.0/db_1/bin/hsodbc for SID HSAS400
    the driver does not exist; only the file /oracle/oracle10/10.2.0/db_1/bin/hsodbcO
    Apparantly hsodbc is not supported on this platform. What are the alternatives?
    Thanks in advance,
    Toon

    use DG4ODBC V11.
    DG4ODBC is a real gateway and thus can be installed independantly from the Oracle database; even on a separate machine.
    Using DG4ODBC will allow you to use an Oracle database 9.2.0.8, 10.1.0.5, 10.2.0.3 (pay attention, these Oracle database requires a compatibility patch) or an Oracle db 10.2.0.4 and 11 (patch already included) to connect to a foreign database using ODBC.
    The connection is then initated by the Oracle db which connects to the gateway listener on a second machine. The gateway listener spawns the gateway executable which loads the ODBC driver and connects to the foreign database.

  • Network cards for Solaris 8 x86

    Which network cards are supported by Solaris 8 x86 ?
    Thank you !
    dorin.

    Are you considering any particular cards ?
    I have had good luck with DEC21040 (10baseT) and DEC21140 (100baseT) cards
    in Solaris 7 through Solaris 10 on x86.
    The same can be said for 3Com 3C905C-TX cards.
    Solaris 8x86 will recognize many chipsets natively,
    and a number of third party developers have created working driver packages.
    Most of their driver packages are free, but a few are not free.
    Solaris 9 works with a few more, and Solaris 10 works with yet more adapters.
    The Solaris 8x86 HCL list has the native cards.
    This other Sun web page can direct you toward 3rd party sites.

  • Map network drive from windows 98 to server 2008 R2

    Guys I have some old Windows 98 systems these 98 systems are attached to pieces of equipment on the warehouse floor. So with that said there is no way to upgrade them. I would like to map a network drive from these 98 systems to a 2008 R2 file server.
    I have played around with LM compatibility mode but I'm not having much luck. Still when I try to access a share on a 2008 R2 box I'm being asked to entire a password. On the old 2003 server all I had to do was create a local account with the same username
    and password on the 2003 server. So if anyone's done this I would be curious in knowing more. BTW the member server I'm trying to connect to is in a domain and the 98 box is in a workgroup.

    Hi,
    As Windows 98 is such an old system, I may make mistake on suggestions I provided so please just have a try. 
    For old client system like Windows XP, in a workgroup environment we have 2 mentions to share folders.
    1. As you said, create local account with same password on each computers so they can access each other with that account.
    2. Share folders to Everyone (including Guest) and enable Guest account on computers which going to access. 
    You can try to enable Guest account and set a same password on each computer as a test.
    Also in Windows XP we need to modify "Simple File Sharing" option. I cannot confirm if it exists on Windows 98 system but if it does, enable it when trying suggestion 2 and disable it when trying suggestion 1. 
    http://support.microsoft.com/kb/304040/en-us
    If you have any feedback on our support, please send to [email protected]

  • This past month I have been having problems connecting to my home wireless connection. Previously I had no problems whatsoever. I have tried unplugging the wireless router, turning off the wirless airport, deleting the network name from my list of server

    This past month I have been having problems connecting to my home wireless connection. I have a MacBook Pro OSX Version 10.6.8. Previously I had no problems whatsoever. I have tried unplugging the wireless router, turning off the wirless airport, deleting the network name from my list of servers and trying to reconnect this way. These methods have worked temporarily, but the same problem keeps coming back. Most of the time my personal wireless connection does not even come up among the list of available networks. My fellow flatmates have PCs and both of them are able to connect to the network without problem.
    The router is a d-link model DIR-615. I am not tech savy, so if any other information need to be provided in order to better understand my situation, please let me know.
    Please help me!

    If I open the list of networks in a window it says "connection timeout," but if I just select it from the drop down it tries for awhile and then stops with no prompt. When I try to run network diagnostics it says "sorry, we can't connect to the internet" (or some solution-free variation of that)

  • Trusted Extensions not installing correctly - Solaris 10 x86 11/06

    I've installed Solaris 10 11/06 x86 selecting the "development" install, and I assigned 7GB to the root slice and 3GB to /export/home. The install goes fine, so I then install Trusted Extensions. After installing Trusted Extensions and rebooting, the Trusted Extensions CDE desktop is not listed as a login option. The JDS Trusted Extensions desktop is listed, but attempting to login to it gives the error "Your X Server has not been set up with SUN_TSOL extension to login to Trusted JDS. Select ordinary JDS to login", and the login fails. Are there any required steps that are not listed in the documentation, or are Trusted Extensions broken in Solaris 10 version 11/06? Any tips at all are greatly appreciated.

    It took me a few days of headaches, but I finally figured it out! I'm working under VMWare, and installing VMWareTools in Solaris 10 seems to somehow break the Trusted Extensions. There are no errors, the Trusted Extension features just don't work. When I installed the Trusted Extensions first I did get the Trusted CDE desktop and it logged in just fine, but after installing VMWareTools the desktop option disappeared from the login menu. I hope this helps someone else.

  • 3-Com NIC Card Networking Problems on Solaris 10 (x86)

    Hi,
    I have Solaris 10 OS installed on a PC. I am having trouble getting my machine to ping other machines on the same network. I have executed the following commands:
    #ifconfig elxl0 plumb
    #ifconfig elxl0 192.168.100.181 netmask 255.255.255.0 up
    When I try to ping another machine on the same lan, I don't get a response. I have even did a the sysconfig command and reconfigured my networking and it still does not work. I have tried different network cable as well. I have looked in the master file. I see the driver for my NIC, so I know it is supported by Solaris 10. Can anyone help me?

    Here is some more info on my problem and a couple of things I have tried to do to resolve the issue :
    I executed the command "prtconf-pv". I found information on my NIC Card, which is a 3-Com 3C905B-TX Etherlink XL 10/100. I found my vendor id - 10b7 and my device id - 9055. I then checked "driver_aliases" file to see if I could find an entry in this file and I did see my vendor id and device id. I would then conclude that Solaris knows my PCI vendor/device-id combination and maps them to elxl driver.
    I have also tried a different cable that i know works and still nothing.
    I also found from research in Sol. 10 that there is file in addition to hosts, hostname.elxl0, defaultrouter that has to be modifed. That file is ipnodes. I checked the file, and my ip address / hostname is noted in the file. Is it possible I have a bad NIC? I thought about swapping it out for another one that I know works, but it is an onboard NIC. Well, if anyone has and additional info, I would greatly appreciate it.

  • Install on Solaris 9 x86 error - help

    when i run the ./setup error show up
    # ./setup
    ./setup: syntax error at line 1: `(' unexpected
    please help
    thank a lot

    not supported on solaris x86 yet. wait for upcomming news from sun on solaris x86 support for as7

Maybe you are looking for