This is a discussion on Re: E450 / Solaris 2.7 network problems within the Sun Solaris Hardware forums, part of the Solaris Operating System category; --> Andrew Tyson wrote: > > Hi, > > Recently (in the last week or so) an unusual network issue ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Andrew Tyson wrote: > > Hi, > > Recently (in the last week or so) an unusual network issue has affected an > E450 at my work. Andrew, the first thing to check is to make sure the autonegotiation settings agree on both ends of the wire. Make sure that both the E450 and Cisco are set to autonegotiate 10/100 and half/full-duplex, OR hardwire both ends to the same settings. I prefer the former, myself (auto). Also, check to see if there are patches in Solaris 7 for the hme driver. The recommended cluster may not include them. Good luck! -- Griff Miller II | | Manager of Information Technology | If you're too open-minded, | Positron Corporation | your brains might fall out. | griff.miller@positron.com | | |
| ||||
| > Andrew, the first thing to check is to make sure the autonegotiation settings > agree on both ends of the wire. Make sure that both the E450 and Cisco > are set to autonegotiate 10/100 and half/full-duplex, OR hardwire both > ends to the same settings. I prefer the former, myself (auto). > > Also, check to see if there are patches in Solaris 7 for the hme driver. > The recommended cluster may not include them. Griff, We actually went through all this ..played with /dev/hme settings, installed patches ... to no avail. In the end a kind soul hit the nail on the head. The problem turned out being a reverse DNS issue with DHCP allocated machines on our LAN. Updating /etc/resolv.conf and including the local DNS host fixed the problem. The wierd thing was that the file had not been changed for months, and suddenly the problem appeared. We think that it may be related to some change with the DNS from our ISP. Thanks and regards, Andrew |