Problem with network card
Hi guys, This message is not actually a Linux based question, but is still "nix". I have recently installed Solaris 8 (for Intel) on a PC at work and am having problems connecting to the network. I think that the problem is related to the speed that the NIC is trying to use when connected to the LAN. I suspect this because the little green speed indicator for 100mb is illuminated (on the NIC) when the workstation is connected to the network jack. Here are some supporting details that I hope someone might find useful: Hardware: HP Vectra Vli8DT (733mhz) Solaris 8 for Intel 3com Etherlink XL PCI NIC ifconfig -a elxl0 flags=100843<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 172.17.24.76 netmask ffffff00 broadcast 172.17.24.255 ether 0:1:3:68:1b:f3 netstat -rn Routing Table: Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 172.17.24.0 172.17.24.76 U 1 2 elxl0 224.0.0.0 172.17.24.76 U 1 0 elxl0 default 172.17.24.3 UG 1 0 127.0.0.1 127.0.0.1 UH 29 1897 lo0 If anyone can help or has similar experience, please give me a shout. I think I remember reading somewhere about a device driver file that can be changed to force the speed of the NIC. Anyone else ?? Thanks. Matthew
On Mon, Jul 09, 2001 at 02:57:32PM -0400, Simoncini, Matthew wrote:
have recently installed Solaris 8 (for Intel) on a PC at work and am having problems connecting to the network. I think that the problem is related to the speed that the NIC is trying to use when connected to the LAN. I suspect this because the little green speed indicator for 100mb is illuminated (on the NIC) when the workstation is connected to the network jack.
Is the network not 100mbit? If the speed is mismatched, you won't be on the network at all. If the duplex is mismatched, you'll just get bad performance when doing certain operations (namely quick read/writes). You can determine this (usually) via "netstat -in" and looking for I/O errors and collisions on a FD network.
If anyone can help or has similar experience, please give me a shout. I think I remember reading somewhere about a device driver file that can be changed to force the speed of the NIC. Anyone else ??
Hmmm. I know relatively nothing about the Intel version of Solaris (I touched it once about 4 years ago), but on Solaris SPARC you would either use ndd to get/set the net driver settings (ala "ndd /dev/hme link_speed") or set the driver's settings via /etc/system: set hme:hme_adv_autoneg_cap=0 set hme:hme_adv_100T4_cap=0 set hme:hme_adv_100fdx_cap=1 set hme:hme_adv_100hdx_cap=0 set hme:hme_adv_10fdx_cap=0 set hme:hme_adv_10hdx_cap=0 As I said, I don't know if this is valid for Solaris Intel, but ... -- Randomly Generated Tagline: "... so people can't look up your skirt I guess... Not that I wear one..." - Prof. Brown about "Modesty Skirts".
Hi
am having problems connecting to the network.
"problems' is a tad vague. Can you ping another computer on the network by ip address (dotted quad)? (see specifics below)
I think that the problem is related to the speed that the NIC is trying to use when connected to the LAN. I suspect this because the little green speed indicator for 100mb is illuminated (on the NIC) when the workstation is connected to the network jack.
I interpret that the opposite way. I believe the card is telling you that it has been able to touch base with the network and the two of them have agreed to use 100 mb. Thus I think the hardware is fine.
ifconfig -a
elxl0 flags=100843<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 172.17.24.76 netmask ffffff00 broadcast 172.17.24.255 ether 0:1:3:68:1b:f3
It looks like the card thinks it has a valid ip address so again I'd like to know if a ping works as the next step.
netstat -rn
Routing Table: Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 172.17.24.0 172.17.24.76 U 1 2 elxl0 224.0.0.0 172.17.24.76 U 1 0 elxl0 default 172.17.24.3 UG 1 0 127.0.0.1 127.0.0.1 UH 29 1897 lo0
I'd try a ping 172.17.24.3 since that seems to be an outside computer on your network. You may already have this solved. I did not see this from the back and forth messages. Just got back to town so decided to put my two-bits worth in just in case I might actually have got the right answer :-) doug -- Douglas R Waud 17 Lantern Lane, Shrewsbury, MA, 01545-2006 http://www.ummed.edu/pub/d/drw/
participants (3)
-
doug waud -
Simoncini, Matthew -
Theo Van Dinter