M2server

[HellzLoose]

solved it, but i have another problem now :P


i changed some ips to like 7201 instead of 7200 and i get no socket error, but i get con closed ingame :P ive tried to change the ports around in mir2.ini but to no avail

They are ports that you are changing not IPs.
You shouldnt need to change any ports around.

[deanfletc]

you should keep the ports to the originals makes things alot easier just change the ip if use are really struggling ill post a working server up again, ull have to instert your own maps npc/market def things like that..... look at my post "Please read this" for more details on it

VirUs

[DrowninG]

cheers dean,


its all sorted i think it has a problem connecting me to the main server tho =/ might be somethin to do with sql possibly,

ive made alot of progress tbh considering i aint done PS's in like 2 year

[deanfletc]

mssql wont stop u connectiong tbh i dont think, itll be ur gates/ip/server name things like that
mssql is just for holding data

VirUs

[DrowninG]

well on selgate.exe it always says ktest, there isnt no option in config to change it :S

[deanfletc]

thats ok its in the source like that its ok

VirUs

[DrowninG]

kk bud,

dean i added you to msn last night dunno if u accepted or not but it says ur name now, was wondering if u could pop on and give us a hand?

cheers

[tarima]

Hiya, did you ever fix this problem I am getting the same thing with the black screen.

EDIT: Made whole post relating to blank screen >> http://forum.ragezone.com/f62/help-blank-screen-248651/

[windy2851]

i have the same problem and all my ips are correct because i took full working set of server files of different computer i have looked everywhere for help and posted a few times so any help would be good also the computer i had working server files on was xp and the new one is vista if that helps

[15/05/2007 08:53:48] Guilds: 0
[15/05/2007 08:53:48] Total Castles: 1
[15/05/2007 08:53:58] Windows socket error: An attempt was made to access a socket in a way forbidden by its access permissions (10013), on API 'bind'

[iNs@nE]

Reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Thats the official Microsoft definition of your problem. Inshort, same port being used already or the IP's are just not set.