Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problems over Windows Server 2008
#1
I'm having some troubles since I formatted my server and installed Windows Server 2008.
I've installed everything needed for the server to work. And it does. It loads/runs like it is supposed to, I've even opened the port so outsiders can connect, and then can. But when a client connects it got stuck on character loading.
I tried connecting a vanilla MSE2 client, and it works normally. So the problem is my game, not the OS.
Well, now I'm really on a dilemma. Whats should I do?
I'm using JetByte Socket Server 1.0 and I think that's the problem...
Now I'm thinking if it is worth using this or there is something better out there.
Reply
#2
IOCP sucks.
Reply
#3
GIAKEN Wrote:IOCP sucks.
Why that?
Reply
#4
This might help

http://www.xtremevbtalk.com/showthread.php?t=285255
Reply
#5
I just saw this article.
It's very old.
I can't find anything that really helps.
Reply
#6
Quote:
I've tried the original COM DLL created to support VB6. I'm unimpressed with the results I am getting, which can freeze up a compiled EXE or crash the IDE. Since the later verions don't offer COM support I think I'll let this fade back into obscurity.

Guess it means you shouldn't use it since that guy himself had major problems with it.
Reply
#7
Ok, but what should I use instead, and no, I'm not going back to simple WinSocket.
Reply
#8
Hmm, follow Spodi's path? "SOX with optimized binary packet sending"
Don't know how he does it though.

Spodi Wrote:SOX is just a nice wrapper for the Winsock API. Theres a few hacks you want to do on the socket itself to get it prepped for a game engine, though. For example, it sends a 4-byte (long) overhead for every SEND command, which is pretty useless for a game server (integer would suffice), the default send/recv buffer comes at 8192 bytes (you'd be fine lowering that to around 512 bytes easily), etc.

And just a heads up, you cant use IOCP with SOX I believe, so you can't have an IOCP server and SOX client, because of the additional header I mentioned earlier.

http://www.planet-source-code.com/vb/sc ... 4&lngWId=3
Reply
#9
Thanks Toni, I'll take a look.
EDIT:
I found this:
http://echostorms.net/Mirage/MS%20Tutor ... s/SOX.html
Seems good.

Downloaded SOX source from this:
http://www.planet-source-code.com/vb/scr...4&lngWId=3
OK, it kind of worked, but I can't manage to send Binary data through the sox.
Any one got any idea?
Reply
#10
Any one got SOX with a WORKING SENDDATA function?
I need binary data ><
Tnx in advance.
Reply
#11
Damn ><
Ok, I found out that the problem is NOT the SOX nor the IOCP nor even WinSock xD
It's some kind of problem with my packet handling.
I'll post the code. Client side is the same things as a simple binary packets client. I add to the header the size of the packet and the packet's code(enum).
The problem seems to be that the packets in win server 2008 are going too fast, somehow really, can't explain, or baaaaaaaaaaaaaaaaaaaaaah, I DON'T KNOW!!!
DAMN THIS IS DRIVING ME NUTS!!!
I'll try to disable Naggle's algorithm.
EDIT:
BTW, sry for triple post >
Reply
#12
Dragoons Master Wrote:Any one got SOX with a WORKING SENDDATA function?
I need binary data ><
Tnx in advance.

Use GOREsock.
Reply
#13
I tried, didn't work. It's some kind of problem I'm having with my server. Maybe is how I handle the packets, but I'm not sure. A vanilla MSE2 works normally, even thou it uses string packets and I use binary.
Reply
#14
Mate, I can guarantee you if it is the OS, it is something to do with Windows Group Policies.

I built and maintain one of the servers at work running windows server 2008 and its a fecking nightmare,

VM a Win2k3 Server image in ubuntu, put a stable distro of windows in a tight little box where it can't hurt anything. You will lose out slightly on hardware accelerated performance but an MS server will not suffer from it - my home server for Mirage Realms is a slow waste of space box built from scrap work parts running ubuntu and a vm of windows xp and lag is never an issue (unless I decide to hammer the torrents).

Also, IOCP has considerable disadvantages when used with vb6 - get rid of it.

:3
Reply
#15
What if I just install WS2k3? I'm aware of this damn compatibility issues.
Reply
#16
Do that.
Reply
#17
I'll try that next weekend, I'm totally out of time right now.
Thanks everybody.
Reply
#18
Fantastic! Windows Application Compatibility Toolkit solved the problem! My server is back online!
Big Grin
Reply
#19
Dragoons Master Wrote:Fantastic! Windows Application Compatibility Toolkit solved the problem! My server is back online!
Big Grin

Awesome! Big Grin
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)