Server is always in Check on client

[TychusFindlay]

Hi everyone,

I set up MHTC files on my VPS (not dedicated) and it looks like everything is working just fine on the server side.

Nevertheless, when I try to log in via my silkroad client , the server is always on check status.


-Some brief information-
Server is Windows 2008R2 64bit.

ON SMC , I started the services for both boxes and changed state to Operating and states are all green.

I setup the windows firewall for ports (I also tried to switch Windows Firewall off completely to rule out the firewall thing but it is absolutely not the case)

I have one ethernet adapter on the VPS which is a virtual adapter.

All modules are added to DEP.

Modules are running with no error.

I checked via TCPView and when client starts I can see the connection is established on gateway server.

I of course, set up certification with my IPv4 IP and all other config files with the same IP.

Since up until that point nothing worked I then started patching Modules with my IPv4 IP thx to Chernobyl's sr patcher but it also didn't help.


It is a very weird situation for me because when I create a virtual machine on my local pc and setup the same server it works like a charm. Nevertheless I need to run this on my VPS so that my folks can join and we can kick a couple of camels' *****.

I hope someone has a clue to help me figure what could be causing this situation.

[TychusFindlay]

Guys, I really hope someone has a clue about this client staying in check problem.. I am pretty sure it is something simple but so far no matter what I tried , it didn't help.

Now I am thinking of trying it on another provider (ie. Azure) .. Anyone ?

[NorseGodTyr]

Originally Posted by TychusFindlay

Guys, I really hope someone has a clue about this client staying in check problem.. I am pretty sure it is something simple but so far no matter what I tried , it didn't help.

Now I am thinking of trying it on another provider (ie. Azure) .. Anyone ?

all ports setup as tcp in firewall ??
15779, 15881, 15884

[TychusFindlay]

Originally Posted by mialuisa

all ports setup as tcp in firewall ??
15779, 15881, 15884

Yes I setup those ports for inbound and outbound. And since they didn't work I disabled windows firewall to check whether it is about it and the situation didn't change.

What I am thinking now is that the files I have been using (MHTC file modules) are somehow set to not serving for WAN IPs.

Eventhough I used SR patcher 1.06 by chernobyl for all modules possible (where I input my IPv4 for modules) and patcher said it was successful in patching them I think it is still the case that modules are not patched correctly.

What I can confirm is that port 15779 is open as Client sees the name of the server (you can check the image on original post) and the SMCupdater is giving the MS info to the client as well. Those are visible to the client side.

But I don't see anything happening on Agentserver for instance..

I feel really stuck into this. Is it possible if anyone can provide me a link with patched MHTC server files somewhere?

I believe some weirdo must have ASM hacked the files for not serving on WAN..(or it is my noobism - my wish)

[JustNrik]

did you start service on smc?

[TychusFindlay]

Originally Posted by JustNrik

did you start service on smc?

I appreciate you are trying to help but I already mentioned that I did it on original post and even shared a screenshot which validates my action. Once again everything is green and server is operational.

Believe me I wish I was running into such a noob pitfall. But apparently I am in a deeper trouble compared to missing to press a button.

yet thank you for the initiative.

Is it likely that I have to use EDXloader for connecting to server on mhtc files?

I m going to puke over those files. I just set them up on azure and the result is same. No port issues .. yet Server looks like it is in check.. I think I will have to learn assembly to fix the modules. =/

[TychusFindlay]

As I guessed, the server modules are modified in such a way that they don't allow WAN access for client and SR patcher was not helping eventhough it says it successfully patches the modules. I was using MHTC files from Lunixx repack.

As soon as I changed my server modules with ECSRO testin (you can find them in the release section) files the client started connecting with no problem.

SOLUTION: Either find unmodified server modules, or patch them yourselves. Otherwise you are going to be limited to LAN play.

#request close

[Spidy.]

^

#Closed