This discussion is archived
1 2 Previous Next 20 Replies Latest reply: Jul 1, 2012 2:12 PM by 926213 RSS

network-problem

926213 Newbie
Currently Being Moderated
Hello,

I had installed the solaris version 10 08/11 on a x68 system. The network card is Intel Pro/1000 CT x1 EXPI9301CT.
The device name for this nic is e1000g2 and has the following configuration:

flags=1000843<UP,BRADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.20 netmask ffffff00 bradcast 192.168.1.255
ether 0:1d:60:4:1d:f0

With the command dladm show-dev, I got the following output:

e1000g2 link: up speed: 1000 Mbps duplex: full

I think, the network configuration lokks fine, but if I try to ping the ip-address of another machine, the command-prompt don't come back and it seems, that the solaris-computer can't reach another machine in the same subnetwork.

Can someone tell me, what the problem for this case is ?


Regards,

user5026906
  • 1. Re: network-problem
    Nik Expert
    Currently Being Moderated
    Hi.

    Please show netstat -nr from you system.

    What IP address used for test ?
    What OS on test system ? Firewall on test system switched off ?


    Regards.
  • 2. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    user5026906 wrote:
    Hello,

    I had installed the solaris version 10 08/11 on a x68 system. The network card is Intel Pro/1000 CT x1 EXPI9301CT.
    The device name for this nic is e1000g2 and has the following configuration:

    flags=1000843<UP,BRADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 192.168.1.20 netmask ffffff00 bradcast 192.168.1.255
    ether 0:1d:60:4:1d:f0

    With the command dladm show-dev, I got the following output:

    e1000g2 link: up speed: 1000 Mbps duplex: full

    I think, the network configuration lokks fine, but if I try to ping the ip-address of another machine, the command-prompt don't come back and it seems, that the solaris-computer can't reach another machine in the same subnetwork.

    Can someone tell me, what the problem for this case is ?


    Regards,

    user5026906
    Hello,

    the output of the command netstat -rn is the following:

    # netstat -rn

    Routing Table: IPv4

    Destination Gateway Flags Ref Use Interface

    -------------------- -------------------- ----- ----- ---------- ---------

    192.168.1.0 192.168.1.20 U 1 0 e1000g2

    224.0.0.0 192.168.1.20 U 1 0 e1000g2

    127.0.0.1 127.0.0.1 UH 4 122 lo0


    The IP-address for the solaris-machine is 192.168.1.20.

    The other IP-address, that I use is 192.168.1.10. This is a IP-address from a network-printer.

    I tried it with a notebook, that is in the same subnet. This IP-address is 192.168.1.23, but this is in opposition to the printer not a static address. This notebook got the IP-address from a DHCP-server,
    that is a router too.

    Between the printer and the solaris-computer is a switch with the IP-address 192.168.1.254.

    Regards,

    Frank
  • 3. Re: network-problem
    bobthesungeek76036 Pro
    Currently Being Moderated
    My next step would be swapping out the switch
  • 4. Re: network-problem
    Dude! Guru
    Currently Being Moderated
    Are you sure about the subnet mask? That's a huge range. I think something like 255.255.255.224 was probably more appropriate if you use a VLAN, which defines the range 192.168.1.1 - 192.168.1.30, for instance.
  • 5. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    Hello,

    I can't reach the switch with the command ping.
    I think, it doesn't matter if I take the switch out of the network.

    Regards,

    user5026906
  • 6. Re: network-problem
    Marty Newbie
    Currently Being Moderated
    Let's rule out one things at a time.

    * Is the Solaris address static or was it set using DHCP?

    If it was set using DHCP then we can assume the Solaris machine is on the LAN, or at least on some LAN with a DHCP server.

    * Is the notebook connected wireless or wired?

    Try making a wired connection with the notebook to the same port using the same cable as the server (after disconnecting the cable from the server, of course).

    Let us know what you learn,
    Marty
  • 7. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    Hello,

    1.) The Solaris address is static with the IP-address 192.168.1.20.

    The solaris computer is on the same LAN like the netbook. It#s even in the same subnet.

    2.) The notebook is connected wired. I try the same wired connection like the one for the solaris-computer to the same port with the same cable.
    It works.

    Additional, I boot the solaris-computer with a Live-CD of Linux. With this OS, I can connect to the internet and therefore I can ping the notebook and the switch.


    Regards,

    user5026906
  • 8. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    The network problem exists furthermore.
  • 9. Re: network-problem
    Marty Newbie
    Currently Being Moderated
    I don't see that you have a default gateway set up. If you are setting up static addresses this can happen. I asked above:
    * Is the Solaris address static or was it set using DHCP?
    Your response did not answer the question:
    The solaris computer is on the same LAN like the netbook. It#s even in the same subnet.
    The question remains, either:

    * The solaris computer is on the same LAN like the netbook. It#s even in the same subnet, and configured static, or
    * The solaris computer is on the same LAN like the netbook. It#s even in the same subnet, and configured with DHCP

    I suspect you have a static configuration and not DHCP.

    Not able to recall the correct syntax for S10, I can only tell you that under S11 the correct command would be:

    $ sudo route -p add default 192.168.1.1

    Substitute the correct address of your gateway. That still does not explain the problem hitting devices on the same subnet. Is it possible two devices have the same MAC address on your LAN?
  • 10. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    Hello,

    I had answered the question with the following statement:

    1.) The Solaris address is static with the IP-address 192.168.1.20.


    If I try boot the machine with the Live-CD of Linux, I can connect to the Internet and can ping the other machines.


    Regards,

    user5026906
  • 11. Re: network-problem
    Marty Newbie
    Currently Being Moderated
    I had answered the question with the following statement:
    My apologies, I missed that.
    If I try boot the machine with the Live-CD of Linux, I can connect to the Internet and can ping the other machines.
    The output of ifconfig says your Solaris MAC address is 0:1d:60:4:1d:f0. Three sites I use show that *00:1d:60* belongs to ASUStek, yet your card is an Intel card. Do you have the same MAC address under Linux?
  • 12. Re: network-problem
    834232 Newbie
    Currently Being Moderated
    Make sure the file /etc/defaultrouter contains the IP address of your router.
  • 13. Re: network-problem
    bobthesungeek76036 Pro
    Currently Being Moderated
    You could also show us what the output of the commmand:

    <pre>grep net /etc/path_to_inst</pre>

    looks like.
  • 14. Re: network-problem
    926213 Newbie
    Currently Being Moderated
    You' re right.

    Here is the output of ifconfig under Linux:

    eth0 Link encap:Ethernet Hardware Adresse *68:05:ca:02:ca:99*
    inet Adresse:192.168.1.22 Bcast:192.168.1.255 Maske:255.255.255.0
    inet6-Adresse: fe80::6a05:caff:fe02:ca99/64 Gültigkeitsbereich:Verbindung
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
    RX packets:5035 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2576 errors:0 dropped:0 overruns:0 carrier:0
    Kollisionen:0 Sendewarteschlangenlänge:1000
    RX bytes:5151685 (5.1 MB) TX bytes:384965 (384.9 KB)
    Speicher:b0220000-b0240000

    The ethernet-address is here: *68:05:ca:02:ca:99*.

    I can change the address with the ifconfig-command temporarely, but this have no effect.
    After the change with ifconfig, I can't ping any other system too and after a reboot it's the same old ethernet-address.
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points