1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice
  3. Greetings Guest, Having Login Issues? Check this thread!
    Dismiss Notice
  4. Hail Guest!,
    Please take a moment to read this post reminding you all of the importance of Account Security.
    Dismiss Notice
  5. Author Wes Locher has teamed up with Stratics for a giveaway of his new book Braving Britannia. This book explores the history and impact of Ultima Online and includes interviews from current and past dev team members as well as many UO and Stratics community members. Click here for more details!
    Dismiss Notice

Slow connection and have tried many things to fix....

Discussion in 'UO Resources' started by gjohnson5, Mar 31, 2010.

  1. gjohnson5

    gjohnson5 Guest

    But still not working
    The following may help some:


    Make sure you have the latest correct driver for your NIC. If the NIC is integrated the driver should be from your PC (or motherboard) manufacturer's web site. If you already have the latest driver use Device Manager to uninstall it; reboot and let Windows discover the adapter and reinstall the driver.

    (From a JohnWill post)

    TCP/IP stack repair options for use with Vista and 7.

    Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

    Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

    Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log

    Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log

    Reboot the machine.

    I would only do this as a last resort personally. The netsh parameters are easy enough to alter
    Also to reset all tcp values to installation defaults use

    netsh int tcp reset reset.log

    the reset.log will dump the results of the command to the file reset.log so you can view at a later time. This can also be something like c:\temp\reset.log if you wish to have a full path to the file....
  2. gjohnson5

    gjohnson5 Guest

  3. gjohnson5

    gjohnson5 Guest