Hazvinei Mugwagwa writes: > Update - I'm not sure whether I have made progress or not, but I am able to > ping and access machines on my network. All the machines are connected to a > Netgear 10/100/1000 switch which in turn is connected to a wireless/wired > linksys router, which is running as a DHCP. I am unable to ping the router or > access the internet.
Ping how? Have you tried "ping -n" to isolate possible name service problems? Have you tried snooping the connection to see what's actually on the wire? > How do I troubleshoot this situation? > > In response to the previous responses, I noticed that my var/adm/messages had > a report that auto-negotiation failed and I used the recommended solution by > adding the following line to nfo.conf "nfo-duplex="Full" nfo-speed=100" (I > have problems setting this to 1000). Oh, ouch! That's almost certainly toxic. When you force duplex and speed, that causes the driver to omit autonegotiation. That will force the link partner into *half-duplex* mode, resulting in terrible performance and very high packet loss rates. If you must force link parameters, then you must do so on *both* ends of the link, not just one. Otherwise, you're in a world of hurt. > Is there a way to see why 1000 does not work? I get 1Gbps with XP no problem > on the same conenction. That sounds like a driver problem. If you can get debug messages from this failure and post them, I think the driver author (not me) might be able to help out. At this point, I think the most likely issue you need to look at is that Ethernet driver and the way it handles the chipset. It doesn't sound stable. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
