RE: Marvell Yukon 88E8053 PCI-E Gigabit Ether net Controller



I would start with updating the driver for the NIC.

If it is a gigabit NIC you should disable some of the advanced features on
the device like "offload tcp/ip checksum", "jumbo frames", etc.

If you can ping localhost then it sounds like your network stack is working
OK. Try a different network cable, switch or hub, etc. Run IPCONFIG /ALL
to make sure that the settings look correct.

Make sure you don't have IPv6 installed.

Try connecting the server to a client machine using a crossover cable to
take some of the other variables out of the loop.

Try replacing the NIC with a different model.


Jim Martin - (MSFT)
jimmart@xxxxxxxxxxxxxxxxxxxx
Microsoft Corporation

.



Relevant Pages

  • Re: Forcedeth driver bug
    ... > Do you really know that the driver don't get the stuck packet. ... I'm not sure it's the driver's fault. ... Such an important bug in the network stack would hardly go unnoticed. ...
    (Linux-Kernel)
  • Re: Using the net on an XT: Drivers & TCP/IP
    ... LanManager network stack and is called netbind. ... driver to the TCP driver, ...
    (comp.sys.ibm.pc.classic)
  • Re: lor on boot
    ... this is because the if_rl driver holds the driver mutex across a ... a call into the remainder of the network stack. ... for you now is that I temporarily enabled direct dispatch of the isr code ... the remainder of the stack, ...
    (freebsd-current)
  • Re: Computer Name
    ... I have a system with a device driver that is loaded before the network stack as KM suggests. ... It reads jumpers on the parallel port connector. ... Then it patches Registry IpAddress and ComputerName according to read value. ...
    (microsoft.public.windowsxp.embedded)