Staying connected

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Staying connected

Post by crazychris »

Ok i've been having a lot of problems with my UO client staying connected. not sure what it is but after playing say 5 to 15 minutes i'll get disconnected or sit there stuck while everyone else is moving around and still talking to me.

I'm using 2 ops systems. Windows 7 32 and Vista 64 bit. Windows 7 32 bit seems to be the best bet. so i have been staying with windows 7 32 bit. my other specs are as follows

Thanks for any help

Computer:
Computer Type ACPI x86-based PC
Operating System Microsoft Windows 7 Professional

DirectX DirectX 11.0


Motherboard:
CPU Type QuadCore Intel Core i7 920, 2800 MHz (21 x 133)
Motherboard Name Dell Studio XPS 435MT
Motherboard Chipset Intel Tylersburg, Intel Nehalem
System Memory 3063 MB (DDR3-1066 DDR3 SDRAM)
DIMM1: Hynix HMT112U6AFP8C-G7 1 GB DDR3-1066 DDR3 SDRAM (7-7-7-20 @ 533 MHz) (6-6-6-18 @ 457 MHz)
DIMM2: Hynix HMT112U6AFP8C-G7 1 GB DDR3-1066 DDR3 SDRAM (7-7-7-20 @ 533 MHz) (6-6-6-18 @ 457 MHz)
DIMM3: Hynix HMT112U6AFP8C-G7 1 GB DDR3-1066 DDR3 SDRAM (7-7-7-20 @ 533 MHz) (6-6-6-18 @ 457 MHz)
DIMM5: Hynix HMT112U6AFP8C-G7 1 GB DDR3-1066 DDR3 SDRAM (7-7-7-20 @ 533 MHz) (6-6-6-18 @ 457 MHz)
BIOS Type AMI (06/05/09)

Display:
Video Adapter
ATI Radeon HD 4800 Series (512 MB)
Video Adapter
ATI Radeon HD 4800 Series (512 MB)
3D Accelerator
ATI Radeon HD 4850 (RV770)

Multimedia:
Audio Adapter
ATI Radeon HDMI @ ATI RV770/790 - High Definition Audio Controller
Audio Adapter
Realtek ALC888/1200 @ Intel 82801JB ICH10 - High Definition Audio Controller

Network:
Network Adapter Intel(R) 82567LF-2 Gigabit

Peripherals:
FireWire Controller VIA OHCI Compliant IEEE 1394
Image
UO Gone Right
Image
UO Gone Wrong

orionsune
UOSA Donor!!
UOSA Donor!!
Posts: 241
Joined: Wed Feb 04, 2009 9:11 am
Location: NC
Contact:

Re: Staying connected

Post by orionsune »

You can try assigning the "resync" function of razor to a hotkey, and when you experience the freeze, try resyncing your client with the hotkey.

You can also disable "Smart CPU Reduction" outlined in this post... http://forum.uosecondage.com/viewtopic.php?f=32&t=13814

If you go to a command prompt and try pinging the server.

Code: Select all

ping uosecondage.com
Image

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

Ok i tried the pinging and everything went good. use smart cpu usage reduction has been checked off. as for the resynchronize i'm not sure if it is working or not. i found something to set it as a hotkey? is that the only place to find it?

and with that said for me to play i have to push that every say 10-15 minutes? there has to be a better way to fix it.

any other ideas? the resync may work not sure i have to try it more and see if it works...
Image
UO Gone Right
Image
UO Gone Wrong

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

oohh and after just about 30 minutes of play - letting it marco using the resyc stuff added in it still disconnected...

just to recap on that i was moving around the brit bank and still got disconnected using resyc.

Thanks for any and all help ;D
Image
UO Gone Right
Image
UO Gone Wrong

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

I Also did a trace after looking around online to see if anything else could help me out...

C:\Users\chris>tracert uosecondage.com

Tracing route to uosecondage.com [64.34.176.148]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 5 ms 5 ms adsl-145-34-1.mia.bellsouth.net [Home IP* was removed]
3 9 ms 7 ms 5 ms 205.152.108.1
4 8 ms 23 ms 7 ms ixc00mia-ge-0-2-2.bellsouth.net [205.152.145.25]

5 12 ms 14 ms 13 ms 12.83.4.88
6 47 ms 96 ms 13 ms 12.83.4.205
7 15 ms 23 ms 29 ms 12.83.9.73
8 14 ms 15 ms 12 ms 74.175.192.126
9 * 49 ms 66 ms cr2.ormfl.ip.att.net [12.123.34.134]
10 * 65 ms 47 ms cr1.attga.ip.att.net [12.122.5.142]
11 45 ms 50 ms 51 ms cr2.wswdc.ip.att.net [12.122.1.174]
12 51 ms 58 ms * gar1.ascva.ip.att.net [12.122.134.129]
13 48 ms 43 ms 42 ms 12.118.44.50
14 70 ms 51 ms 42 ms 10ge.ten1-2.wdc-sp2-cor-1.peer1.net [216.187.115
.234]
15 43 ms 42 ms 50 ms 216.187.120.230
16 47 ms 51 ms 47 ms uosecondage.com [64.34.176.148]

Trace complete.
Image
UO Gone Right
Image
UO Gone Wrong

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

i did it again just for kicks and got this, this time.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\chris>ping uosecondage.com

Pinging uosecondage.com [64.34.176.148] with 32 bytes of data:
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Request timed out.

Ping statistics for 64.34.176.148:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 51ms, Average = 47ms
Image
UO Gone Right
Image
UO Gone Wrong

Hicha
UOSA Donor!!
UOSA Donor!!
Posts: 2264
Joined: Tue May 05, 2009 10:03 am
Location: out selling permits

Re: Staying connected

Post by Hicha »

Open two command prompts, run this in the first one: ping uosecondage.com -t

In the second one, type tracert uosecondage.com, and as soon as you see "Request timed out" in the first one, run the second one and see if your connection is getting dropped somewhere along the line.
Image
"I consider most of you NPC's that inhabit the single player game that I am here to enjoy." - MatronDeWinter

orionsune
UOSA Donor!!
UOSA Donor!!
Posts: 241
Joined: Wed Feb 04, 2009 9:11 am
Location: NC
Contact:

Re: Staying connected

Post by orionsune »

I know your specs only list one network card, but i'm asking anyways, are you using a wireless network?

Do you have another computer you can put UO on and see if you get the same results?
Image

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

I have a Hard Line to my router which goes to the network.

The router has the ability to go wireless.

and for the command just pinging unless, i did that it times out every so often, i tried running the trace when it did but it doesn't seem to find any problems... i'll keep trying that and see if anything comes up but ya.

as for playing it on another computer my family has more then one but they don't want me loading stuff and playing UO on their computers.

just a thought, i installed UO using the UO gold free download i got like a few years ago when shadows was coming out or was it samurai or something. I could reinstall using my CD i got for UO back in 1990S if i can find it, would that make a difference? :?:

thanks :mrgreen:
Last edited by crazychris on Thu Mar 25, 2010 1:14 pm, edited 1 time in total.
Image
UO Gone Right
Image
UO Gone Wrong

Hicha
UOSA Donor!!
UOSA Donor!!
Posts: 2264
Joined: Tue May 05, 2009 10:03 am
Location: out selling permits

Re: Staying connected

Post by Hicha »

crazychris wrote:just a thought, i installed UO using the UO gold free download i got like a few years ago when shadows was coming out or was it samurai or something. I could reinstall using my desk i got for UO back in 1990S if i can find it, would that make a difference? :?:

thanks :mrgreen:
Yes that will definitely make a huge difference as incorrect versions can cause major conflicts and/or disconnects and lag.

I recommend uninstalling UO/Razor/UOAM, then use the download link here and run that installer.
Image
"I consider most of you NPC's that inhabit the single player game that I am here to enjoy." - MatronDeWinter

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

so even if the client says its updated to 6.0.0 you think the file i used to install would be the problem? :?:
Image
UO Gone Right
Image
UO Gone Wrong

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

ok i downloaded and tried the UO from the website and i'm still getting the disconnect problem...

i was hoping that was the simple fix but doesn't look like it. Any other ideas for me to try out.

Oh also quick question. when i installed their UO it asked me if i wanted to install razor from their thing, i didn't i just used my uptodate one i got from razor's website? does that matter any?
Image
UO Gone Right
Image
UO Gone Wrong

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

ok after playing for a little and then having major connection problems i run the Ping thing again and this is what i ended up with. i was connecting and being disconnected while doing this for say 10 or more minutes. and sorry i forgot to run a trace.

Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Request timed out.
Request timed out.
Request timed out.
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Request timed out.
Request timed out.
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=56ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=42ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=60ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=60ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Request timed out.
Request timed out.
Reply from 64.34.176.148: bytes=32 time=1049ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=56ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=43ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Reply from 64.34.176.148: bytes=32 time=1052ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Request timed out.
Request timed out.
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=56ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Request timed out.
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=60ms TTL=112
Reply from 64.34.176.148: bytes=32 time=52ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=47ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Request timed out.
Request timed out.
Reply from 192.168.1.100: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=48ms TTL=112
Reply from 64.34.176.148: bytes=32 time=51ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=44ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Reply from 64.34.176.148: bytes=32 time=54ms TTL=112
Reply from 64.34.176.148: bytes=32 time=45ms TTL=112
Reply from 64.34.176.148: bytes=32 time=50ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=53ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=49ms TTL=112
Reply from 64.34.176.148: bytes=32 time=55ms TTL=112
Reply from 64.34.176.148: bytes=32 time=46ms TTL=112
Image
UO Gone Right
Image
UO Gone Wrong

orionsune
UOSA Donor!!
UOSA Donor!!
Posts: 241
Joined: Wed Feb 04, 2009 9:11 am
Location: NC
Contact:

Re: Staying connected

Post by orionsune »

Your issue is going to be a network problem. Not your game, re-installing the game will do nothing for you.

Have you tried pinging other servers like google.com? Do you get a bunch of no replies?

Do you have another PC you can ping uosecondage from?

Can you try plugging your cable/dsl modem directory into your PC and ping uosecondage.com? Be careful doing that because it will expose your PC to the internet, so make it real brief if you test this way.
Image

User avatar
crazychris
Posts: 10
Joined: Tue Mar 23, 2010 1:26 am

Re: Staying connected

Post by crazychris »

mmmm i was pinging both uosecondage.com and google.com and i 3 time outs, together. other then that i had very few timeouts from google.com i'd say 4 or 5 out of 140. last night me and another player did a few things like open ports for uosecondage.com it seems to have helped a bit i'm not dropping as much i think. not sure tho still need to do more testing today. :roll:
Image
UO Gone Right
Image
UO Gone Wrong

Post Reply