tried everything ppl have suggested

rodders · Post by **rodders** » Wed Sep 20, 2006 8:37 am

Windows Version (and Service Packs):xp pro sp2
Processor Speed:amd athlon 64 3200+ (venice)
RAM:1.5gig ddr
Video Card (Make and Model#):ati radeon 9600 xt
Sound Card (Make and Model#):onboard
Connection Type (Dialup, Cable, DSL, other):adsl2
Modem (Make and Model#):speedtouch 510 v6
Router (Make and Model#):netgear rp614 v2
Internet Service Provider(company name):bulldog
Location(State/Province/Locality, and Country):wales, UK

Problem Encountered at Step #: 8
Which Program (ASGS/Allegiance):allegiance
What Error Message:failed to connect to lobby
Comments (What you tried, description, etc): i have forwarded the needed ports (2300 - 2400) both udp and tcp (as my router does both by default)
it has been put down to the router why i cant play because if i conect directly to the modem i can play allegiance, but there are another 2 pcs which need the net so i am having to use the router to get all 3 online.

I have no other problems with anything else that is done online.

yes i have forwarded ports properly (i have done plenty of port forwarding and everything else works)
my home network runs fine (all ips are reserved on the router)
i have also tried dxport but get no further with it

i have gone through the knowledge base but nothing has changed so im still stuck

need any extra info let me know

------update------

after playing with my modem and router i have managed to move a step further

now the error i get is "guaranteed message could not be delivered" when it tries to log into the lobby

Grimmwolf_GB · Post by **Grimmwolf_GB** » Wed Sep 20, 2006 1:53 pm

the new error message suggests a problem with the forwarding of the UDP Ports.

Post by **Tigereye** » Wed Sep 20, 2006 2:40 pm

Yep. If you get that message every time you are trying to log in, it means you are forwarding TCP fine, but are not forwarding UDP.

Doublecheck your router's port forwarding rules.

--TE

rodders · Post by **rodders** » Wed Sep 20, 2006 3:34 pm

i have checked and double checked everything, only time i was able to actually to get it to work is if i open every port up which isnt the safest thing to do

Dogbones · Post by **Dogbones** » Wed Sep 20, 2006 8:39 pm

What firmware are you running on the netgear? Version 5.2 is the latest.

Buggy router? sounds like it is not forwarding udp and tcp like it is supposed to.

RPC14v2 support page

Psychosis · Post by **Psychosis** » Wed Sep 20, 2006 8:56 pm

have you toggled uPnP? its the idiot switch that sometimes works, and often gets overlooked.

rodders · Post by **rodders** » Thu Sep 21, 2006 3:23 pm

firmware is the latest one, upnp has been toggled (i actually get slightly better results with it turned on)

Dogbones · Post by **Dogbones** » Thu Sep 21, 2006 6:57 pm

Okay, you know it works without the router, so buy a new stinking router /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Although unless it is a bugged or braindead router, someone here should know how to configure your netgear to work.

ImmortalZ · Post by **ImmortalZ** » Fri Sep 22, 2006 3:03 pm

It's bugged and braindead. We've had the entire networking wing of RT and myself on his case. The router refuses to co-operate /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />.

Grimmwolf_GB · Post by **Grimmwolf_GB** » Fri Sep 22, 2006 6:06 pm

Netgear has some of the worst models I have encountered so far. My impression is that ALL hardware routers suck. The only difference is the degree in which they suck.
Damn shame a Linux 486 Disk router consumes so much power, otherwise I would revert to that.