Hello! Need some help here.

05/18/2008 08:29 crilldone2#1
I'm having some kinda problem here with my SRO. It shows that silkroad is undergoing inspections or updates, already for 2 days for now, but actually it's now, my friends can play etc... I already deleted install. Btw im using this same no dc client, Greyfox's. I tried to download different no dc clients, but it didn't change anything. And I have SRO version 1.145. Can sb help me? Don't know what's going on. It's since 16th May 2008, and now 2 days already. I one time had this same problem, then i downloaded like some months later SRO again, when there had been one-billion-trillion-megamillon updates already, then it worked. Is there any other solution?
05/18/2008 09:25 andypockett92#2
check your firewall settings, antivirus settings to see if theyre blocking the client
if everything is okay you could go and check your hosts file ... (C:/WINDOWS/system32/drivers/etc) (open with notepad) ... there should be only the localhost, no other gwgt joymax i dont know what ( usualy u need to add those for the sremu to work)

andy Q, ask me.... GL

EDIT: You should also check if your media.pk2 is patched to work with nubot ... or if youre using loader, check if its auto redirecting the client ...
05/26/2008 10:50 dealio#3
Alright...
05/26/2008 16:20 angusszz#4
you could also just install sro with no bots or so and see if it works then add them.....could even be your connection =)
05/26/2008 16:23 Dark_Xero9#5
its the same problem im getting
05/26/2008 16:47 Dark_Xero9#6
its a bug on sro sry for double post
05/27/2008 01:38 yahmoo123#7
I have been having the same problem.
05/27/2008 08:14 HexCon#8
yeah ver. 1.151 is messed up bretty hard. :/ it took 7h to log in yesterday.... and when i got in.... after 5 sec DC :S
05/28/2008 21:49 yahmoo123#9
the patch they did yesterday i think fixed that problem
05/30/2008 20:01 Lan_Pan#10
what char is better ? chi or euro ?
05/31/2008 00:30 SmilePunk#11
each char has their pros and cons it depends in your style playing
05/31/2008 02:14 kaatze#12
it was a bug in the login but i guess that problem is now fixed :)