TF2 Connection Problems...

Jingo...

Jingo...

Jingo...

Soldato
Joined
12 Sep 2007
Posts
2,666
After a new harddrive & reinstallation of Steam & TF2, I seem to be plagued by "Connection Problem" roughly 10/15 seconds after getting into any Team Fortress 2 game...

Everything else on the computer seems fine, internet connection doesn't seem to be dropping at all, all TF2 settings are as they were before (to my best recollection anyway) yet I cannot seem to get into a single game! :confused:

Am I missing something vital here, or is there anything out there that could be having such detrimental effect?

Any help would be most appreciated,

Cheers,

J
 
I had that problem with my BT Home Hub. It was fixable by telneting into it and changing some settings, but the firmware has been updated since then preventing me from doing so.
 
Here's how to fix it if you are able to telnet: http://forums.overclockers.co.uk/showpost.php?p=10332735&postcount=15

I have a BT HomeHub and using telnet to change the setting works perfectly. BT have disabled telnet on the recent firmware updates so there is no way around this problem which is very annoying. There is a way to force the hub into recovery mode and push the 6.2.2.6 firmware to it which has telnet enabled, this is what I have done as well as disable remote update on the hub so it doesn't upgrade itself.

The problem affects Speedtouch routers (which the BT HomeHub is based on). A lot of ISP's also use Speedtouch routers branded with their own names such as Bethere's BeBox.

I don't fully understand what causes the problem but it's something to do with the router having 'helper ports' configured on ports that the Source engine uses for multiplayer including just listing the servers. My BT HomeHub would physically reboot from just doing a server list refresh in TF2 which should never happen on any router, my BeBox had the connection issues but never reboot itself.
 
Thank you, RobH! I've spent so long trying to fix this problem and then, when I did find a fix, I was no longer able to apply it after the firmware update. Thank you very much!
 
Thanks for all of the advice RobH- I have however managed to find an alternative to your solution.

I accessed the Homehub > advanced > game & application sharing > added "Half-Life2" under my device, then cloned the Half-Life2 application as "HL2" and added it to my flatmates device.

An additional clone for each device accessing the network & presto - we had our flat back on dustbowl last night :)
 
Yeah I did the application sharing on my HomeHub which did fix it, however my HomeHub would reboot over 10 times a day on the newer firmware because of issues with WPA and wireless clients so my IP address would often change and the hub would assign the gaming profiles to other devices. The fix above is a more permanant fix if you are able to use telnet and you no longer need to do port forwarding.
 
RobH, I'm having some trouble rolling back the firmware on my Home Hub and I was wondering if you could give me a hand.

I've been following this guide. It finishes the "Installing new firmware on your device stage" (albeit very quickly, so maybe it doesn't actually finish, but it reaches 100%), then before I get the opportunity to press [Next] it says "Firmware recovery failed. The following error has occured: The upgrade process failed."

This is the same error it shows in step 11 of that guide, except it's not because the wizard didn't detect the device.

This is what is says in the log:
Starting with options: serialFilter=* buildImageName=6226_bant-z_Live.bli
Starting device search.
Found device with serial: SpeedTouch [0723FHSA6]
Starting build check.
Using build image: C:/Documents and Settings/[User]/Desktop/HubFirmwareRecovery_6226/BTHHrecover_Win_v55 with 6226/RecoveryTool/../BThubSW/6226_bant-z_Live.bli
Starting upgrade.
Discovering device.
Starting actual upgrade.
ERROR: Upgrade failed (File error during image file transfer)
End.
Click to expand...

I'll also add that I tried pressing and holding the "Wireless Association" button, unplugging and reconnecting the the power and then releasing it after 5 seconds as detailed in step 11, but to no avail.

Have any ideas?
 
Last edited:
Did you configure you network adapter with a static IP address and connect it to you computer with a network cable (patch cable not a crosssover)? Try and force it into recovery mode as well because this may work, I know mine didn't downgrade on the first attempt, give it a few goes.
 
I used a desktop connected to the hub using a patch cable via the "Ethernet 1" port. I also configured the static IP address as shown in that guide. How exactly do you force it into recovery mode? I'm sure I was doing it correctly, but you never know!

Thanks again for your help.
 
Well assuming you have a version 1 hub you power on the hub, hold down the "Wireless Association" button, keeping the button pressed, unplug the hub, then plug it back in still holding the button and then wait for about 10 seconds. Quckly fire up the recovery tool and start it running.
 
RobH said:
Well assuming you have a version 1 hub you power on the hub, hold down the "Wireless Association" button, keeping the button pressed, unplug the hub, then plug it back in still holding the button and then wait for about 10 seconds. Quckly fire up the recovery tool and start it running.
Click to expand...

Hmm, that's exactly what I tried. This is getting rather annoying. I think I'll just have to plug in my DLink router whenever I want to play the game like I used to do when I got these connection problems.
 
You must log in or register to reply here.
Back
Top Bottom