DS Packet Size Error.

[annoyinglyUgly]

What causes DS Packet Size Error? Map console writes it when trying to log into the map from the character selection screen. It gets stuck at "connecting".

@

(( Please help

Does this mean the NDServer.exe is bad? Does this mean the client is bad?

[heineken0801]

this post is better than these others.
could you try to open ndreg.xng? not NDreg editor just edit IP.

[annoyinglyUgly]

Originally Posted by heineken0801

this post is better than these others.
could you try to open ndreg.xng? not NDreg editor just edit IP.

I mean...it has something to do with ndreg? I have the correct IP's in there. Could you elaborate please?

[madmerlin3009]

Originally Posted by annoyinglyUgly

What causes DS Packet Size Error? Map console writes it when trying to log into the map from the character selection screen. It gets stuck at "connecting".

@

(( Please help

Does this mean the NDServer.exe is bad? Does this mean the client is bad?

Since all the 23 maps are linked to the central hub [DS_SERVER_US.EXE] the ds server is not communicating with ndserver correctly. As the error says the packet size is incorrect.nd server is trying to communicate with central hub to link back to all the other maps


You will notice on each map boot. the nd server comms with ds server and ds server comms back to show existing maps open. It will be the ds server not been able to recognise the packet length

[annoyinglyUgly]

Originally Posted by madmerlin3009

Since all the 23 maps are linked to the central hub [DS_SERVER_US.EXE] the ds server is not communicating with ndserver correctly. As the error says the packet size is incorrect.nd server is trying to communicate with central hub to link back to all the other maps


You will notice on each map boot. the nd server comms with ds server and ds server comms back to show existing maps open. It will be the ds server not been able to recognise the packet length

But I've compiled a lot of DS servers (DS_SERVER_vina, _nexon, _opentest, etc) and it always says packet size's too big. So it means the NDServer.exe is bad? I don't have source code for NDServer so I can't fix that.

[madmerlin3009]

Originally Posted by annoyinglyUgly

But I've compiled a lot of DS servers (DS_SERVER_vina, _nexon, _opentest, etc) and it always says packet size's too big. So it means the NDServer.exe is bad? I don't have source code for NDServer so I can't fix that.

It's a case of one or the other is incorrect. Let me presume the source of DS server source you had was possibly a different revision to the actual code used to compile and link to exe file.nust maybe they altered the packet lengths through time cycle of development of ds server and ndserver life cycle

[annoyinglyUgly]

Originally Posted by madmerlin3009

It's a case of one or the other is incorrect. Let me presume the source of DS server source you had was possibly a different revision to the actual code used to compile and link to exe file.nust maybe they altered the packet lengths through time cycle of development of ds server and ndserver life cycle

I used these files:


Initially I used the original server exes that came with it and that includes the ds server too. But I get the exact same error with the original DS server exe so that's why i compiled a few others. So the DS_SERVER and NDServer do not match, apparently. Great ,I don't even know where to get NDServer exe source from.

If that is the case, there must be a way to alter packet length inside the DS_SERVER source as well because there's two parts to the story (DS and NDServer). How do I know what values to change?

[madmerlin3009]

Originally Posted by annoyinglyUgly

I used these files:


Initially I used the original server exes that came with it and that includes the ds server too. But I get the exact same error with the original DS server exe so that's why i compiled a few others. So the DS_SERVER and NDServer do not match, apparently. Great ,I don't even know where to get NDServer exe source from.

If that is the case, there must be a way to alter packet length inside the DS_SERVER source as well because there's two parts to the story (DS and NDServer). How do I know what values to change?

Well to be honest if you use wireshark to monitor packets being transmitted from these ports 25001-25023 depending on your configuration on a robust operating 9dragons server. look at the packets sent from these ports direct to ds server port you assigned. then look at transmitted and received. i wont say any more. that is just a heads up clue