Fortress server connection issues

[lordpain]

I installed a server according to this (http://www.fortress-forever.com/forum/showthread.php?t=11029) guide.

Server:
2.4 GHz AMD cpu
1GB Mem
100/100 MBit connection
30GB free on the disk volume
Windows XP SP2 (Windows 'Firewall' disabled)
HLDStool --> newest version
FF 2.3 Server
The server is at an off site location

Installation:
d:\HLServer\hldsupdatetool.exe -command update -game hl2mp -dir d:\HLServer

Start up parameters:
d:\HLServer\srcds.exe -console -game FortressForever +maxplayers 16 +exec server.cfg +map ff_well

Server.cfg

//!! BDFC FORTRESS !! SERVER.CFG
hostname " !! [BDFC] Fortress Server !!"
//================================================== ==
sv_password "<HIDDEN>"
rcon_password "<HIDDEN>"
//================================================== ==
mp_timelimit 30
mp_friendlyfire 1
//================================================== ==
cr_scout 0 // Scout class limit. -1 for none allowed
cr_sniper 1 // Sniper class limit.
cr_soldier 0 // Soldier class limit.
cr_demoman 0 // Demoman class limit.
cr_medic 0 // Medic class limit.
cr_hwguy 1 // HWGuy class limit.
cr_pyro 0 // Pyro class limit.
cr_spy 1 // Spy class limit.
cr_engineer 2 // Engineer class limit.
//================================================== ==
sv_rcon_maxfailures 3
sv_alltalk 0
sv_voiceenable 0
//================================================== ==
mp_allowspectators 1
mp_footsteps 1
sv_mincmdrate 0
sv_maxcmdrate 80
sv_minupdaterate 10
sv_maxupdaterate 100
sv_minrate 2000
sv_maxrate 20000
sv_unlag 1
sv_maxunlag 0.3
sv_spectatorchat 1
sv_cheats 0
sv_allowupload 1
sv_allowdownload 1
sv_voicecodec vaudio_speex
sv_specaccelerate 5
sv_specspeed 2
//================================================== ==
log on
sv_logbans 1 // Log bans?
sv_logecho 0 // Log echos?
sv_logfile 1 // Make logfile
sv_log_onefile 1


Network:
Ports opened in FW:
27005 - 27020 TCP
27005 - 27020 UDP

Issue:
The server is visible in the server list online on the clients.
When I connect to the server I can see on the console that I'm connected, my Steam ID validated etc.
But on my client it hangs at about 4 'blocks' on the loading screen.
When I connect to a different server I have no probs.
The weird thing is that a friend of mine CAN connect to the server without probs.

What did I try:
* Both Client & Server in DMZ: no result
* Re-install FF on Server & Client FF: no result
* Sv_lan 0 parameter: no result
* Starting the server with the +ip parameter: no result

I'm kinda running out of ideas :cry:

The weird thing is that even DMZ didn't solve my problem...
And a friend of mine can connect without problems, he also connects via the internet (not via LAN).

[Dr.Satan]

is it hanging on the "sending client info" part? And how long do you give it before giving up?

[lordpain]

is it hanging on the "sending client info" part? And how long do you give it before giving up?

The text 'sending client info' shows up for like a sec just right of the loading status bar, then disapears again.

I let it 'connect' for about 10 ~ 15 mins to see if it actually did something.
My friend confirms that ingame it says 'Lord Pain joined the game'.

I'm not sure if this is a client or a server issue thou

[Dr.Satan]

This sounds like a client issue. Try doing the stuff in this(click) (http://forums.fortress-forever.com/showthread.php?p=442534) thread and see if it helps you.

Edit: if not then we'll try some other stuff.

[lordpain]

This sounds like a client issue. Try doing the stuff in this(click) (http://forums.fortress-forever.com/showthread.php?p=442534) thread and see if it helps you.

Edit: if not then we'll try some other stuff.

I'll try the cl_forcepreload 1 tonight :)

[Dr.Satan]

I'll try the cl_forcepreload 1 tonight :)

yeah test out the heapsize too...that shit helped me out sooo much on load times!

[hlstriker]

Are you hosting the server at home on the same router you use for your gaming rig?

If so make sure the server and your client aren't trying to use the same port.

In your servers startup parameters use -port 27016

[lordpain]

Are you hosting the server at home on the same router you use for your gaming rig?

If so make sure the server and your client aren't trying to use the same port.

In your servers startup parameters use -port 27016

Nope if you have fully read my starting post, the server is on an offsite location, on a different connection, and therefor on a different WAN :)


Edit:
I increased the heapsize to 512MB and must say the overall performance of the client is much much better...
Due to maintenance on the internet connection of the server, I can't it out on our own server :(

[Dr.Satan]

np, let us know when you are able to test.

[lordpain]

Small update:
We decided to start from the ground up with new hardware.
The hardware will be installed today and we'll start rebuilding it this afternoon.
So hopefully we can see this problem resolved tonight :)

[lordpain]

Right, we got a machine & software up and running again....

But when I connect to it I am still stuck at the loading screen after 4 'blocks' of loading??

I R confused :(
http://nefertiti.servegame.com/temp/naamloos.JPG

[hlstriker]

Have you tried connecting through the console?

It also might be worth a shot to not load the banned config even though I doubt it will help anything.

[lordpain]

Have you tried connecting through the console?

It also might be worth a shot to not load the banned config even though I doubt it will help anything.

I excluded the bannedconfig, no help there...
I'll try the connect via console in a sec :)

Edit:
Connecting via the console doesn't work...

I was thinking... The garbage of stuff not found during the server startup shouldn't be a problem I suppose?

[hlstriker]

I was thinking... The garbage of stuff not found during the server startup shouldn't be a problem I suppose?

Nope it shouldn't.

[[AE] 82694]

I probably missed it but whats the server IP in question? Are you hosting this at home or on a box someplace?

Edit: did you install 2.2 first then the 2.3 patch?

[lordpain]

82694;443774']I probably missed it but whats the server IP in question? Are you hosting this at home or on a box someplace?

Edit: did you install 2.2 first then the 2.3 patch?

It's hosted on a dedicated box outside my current network.

I changed the password for the FF server to: tempFF
IP: 195.169.213.39:27015

If needed you can contact me on steam via steam account name: fanghorn

Edit:
Ofcourse I installed 2.2 full first and upgraded it with 2.3

[lordpain]

Hmmm tried some other stuff today like changing some server parameters...
The ones like:
sv_mincmdrate 0
sv_maxcmdrate 80
sv_minupdaterate 10
sv_maxupdaterate 100
sv_minrate 2000
sv_maxrate 20000
sv_unlag 1
sv_maxunlag 0.3

Still no improvement :(

[[AE] 82694]

I connected to your server just fine so it's defiantly a client issue. Not sure why you can connect to others and not your own. try -debug and let it time out when you try to connect. games/fortressforever/properties/set launch options/ -debug

This should create a .mdmp when your client crash's.

[lordpain]

82694;443842']I connected to your server just fine so it's defiantly a client issue. Not sure why you can connect to others and not your own. try -debug and let it time out when you try to connect. games/fortressforever/properties/set launch options/ -debug

This should create a .mdmp when your client crash's.

I un-installed the client, downloaded it again.
Install the 2.2 full, then install the 2.3 patch.

No debug dump :(
As my client won't time-out nor crash.

But I receive the following on the client console:
Received fragment out of order: 35/3
Received fragment out of order: 35/3
Received fragment out of order: 35/3
Received fragment out of order: 35/3
Received fragment out of order: 35/3
Received fragment out of order: 35/3
etc etc etc

[hlstriker]

Sounds like you have packet loss.

Try these steps in order (if one doesn't work go to the next step):

1) If you are using wireless try connecting directly to your router.
- If fixed: Somehow losing packets over air.

2) If you are wired directly to the router try connecting directly to the modem.
- If fixed: Your router has a problem.
+ Try switching the port the cable plugs into.
+ Try resetting your router to factory settings.
+ Try upgrading the routers firmware.
+ Try a different router.

3) Try a different cat5 cable.

4) Try a different ethernet card.

5) Try a different modem.

[lordpain]

Sounds like you have packet loss.

Try these steps in order (if one doesn't work go to the next step):

1) If you are using wireless try connecting directly to your router.
- If fixed: Somehow losing packets over air.

2) If you are wired directly to the router try connecting directly to the modem.
- If fixed: Your router has a problem.
+ Try switching the port the cable plugs into.
+ Try resetting your router to factory settings.
+ Try upgrading the routers firmware.
+ Try a different router.

3) Try a different cat5 cable.

4) Try a different ethernet card.

5) Try a different modem.

Ok took a while to figure it out: Jumbo frames...
I enabled jumbo frames on my gigabit segment to get higher transfer rates.
Due to I dunno what Fortress (read: HL2) can't handle it proper somehow :(

I disabled jumbo frames on my firewall and client....
Result: IT'S ALIVE IGOR!!! ALIVE I TELL YOU :D

Thank you very much for all your support & tips :)

[hlstriker]

Good to hear you got it working :)

Edit: Note that your ISP might not support jumbo frames and that's why you have loss.

[Elmo]

awesome. very happy you've got it all figured out.. I had no clue on the matter :p

[lordpain]

We had some nice load on the server earlier on :)
We're running a 16 slot for test, we might scale up when it is stable.

Tomorrows I'll install the vote stuff etc :D

[Elmo]

what tickrate you running btw? if 33 then change it to 66... FF is just too fast for a 33 tick server.

[lordpain]

what tickrate you running btw? if 33 then change it to 66... FF is just too fast for a 33 tick server.

The tickrate was default (33), I changed it to 66 now :)
I hope it won't crash like saturday :(
It was full house and the server crashed.... Most annoying part: there was no *.mdmp file from it.

[Elmo]

thank you for listening to me!

[[AE] 82694]

It was full house and the server crashed.... Most annoying part: there was no *.mdmp file from it.

add -debug to your s t art up command line. otherwise it wont.

d:\HLServer\srcds.exe -console -game FortressForever +maxplayers 16 +exec server.cfg +map ff_well -debug

[lordpain]

thank you for listening to me!

*cuddles* :D

Anyways: I'm proud to anounce....
The !! BDFC Beer House !! is open for business :D
IP: 195.169.213.39:27015

In case ya ask: BDFC = Beer Drinking Flag Carriers :mrgreen:

82694;444147']add -debug to your s t art up command line. otherwise it wont.


Done :)
Hope I won't need it :P