Free Allegiance Forums

Sorry, I'm out of ideas here Maybe some other guys can help..?

ogorass wrote:QUOTE (ogorass @ Nov 20 2007, 11:39 AM) Sorry, I'm out of ideas here Maybe some other guys can help..?

I am tempted to revert my old machine so i can play... /cry I miss alleg lol

deceit wrote:QUOTE (deceit @ Nov 20 2007, 11:02 AM) I am tempted to revert my old machine so i can play... /cry I miss alleg lol

LMAO, we have the same problem. My vista can't play, so is my new xp. So the only thing that can play is my 2000 that has no powersupply unit and no CPU as I burned it somehow.

I fixed my problem, try opening or closing u're UPNP, see if that helps

Deceit, I'd recommend 2 things:Remove those Port Forwarding rules you added to your Linksys router since they aren't needed by Allegiance. Let's work with a "vanilla" setup.Check your uPNP setting on your Linksys router. Is it on? Turn it off. Is it off? Turn it on. Whatever it is currently set to, toggle it the other way.EDIT: Also, I don't see you trying to log in today at all. You say you were getting a "Client submitted an invalid key" error? I don't see you attempting to log in at all. Which callsign are you using?

Good luck,

--TE

Tigereye wrote:QUOTE (Tigereye @ Nov 21 2007, 06:27 PM) Deceit, I'd recommend 2 things:Remove those Port Forwarding rules you added to your Linksys router since they aren't needed by Allegiance. Let's work with a "vanilla" setup.Check your uPNP setting on your Linksys router. Is it on? Turn it off. Is it off? Turn it on. Whatever it is currently set to, toggle it the other way.EDIT: Also, I don't see you trying to log in today at all. You say you were getting a "Client submitted an invalid key" error? I don't see you attempting to log in at all. Which callsign are you using?

Good luck,

--TE

That invalid key error was when I tried to run it through Microsoft Virtual PC 2007 with XP home on it set up the same way I had my PC setup when it worked. Since it was in an emulated environment, I was almost certain it would fail. Since it has little to do with the problem, I think we should drop it.

In vista it performs the same way with UPnP in an on or off state. Also, I was trying it without port forwarding, so I posted a screenshot of when I tried it with port forwarding. I have also tried purchasing a new router. (this is the one I used port forwarding on.)

In any case, please read the rest of my posts before posting replies and is there anyone here who knows why the client fails to connect?

deceit wrote:QUOTE (deceit @ Nov 7 2007, 12:13 AM) [*]-DMZ on Router (means it put me infront of the router) +++ before this gets accused, Alleg fails to connect to server even when ports are forwarded instead of using DMZ. its some sort of Linksys Wireless G router (wireless disabled).
[/list]

As Ogo said, Get off the DMZ and remove your port forwarding rules.

DrBeginner wrote:QUOTE (DrBeginner @ Nov 9 2007, 03:17 AM) Always run asgs in admin mode. You have to keep on right clicking on it and clicking on "run as admin". afaik there's no way around it atm.

Ignore DrB, You do not have to run ASGS in admin mode.

Tigereye wrote:QUOTE (Tigereye @ Nov 22 2007, 11:27 AM) Deceit, I'd recommend 2 things:Remove those Port Forwarding rules you added to your Linksys router since they aren't needed by Allegiance. Let's work with a "vanilla" setup.Check your uPNP setting on your Linksys router. Is it on? Turn it off. Is it off? Turn it on. Whatever it is currently set to, toggle it the other way.

TE is a legend.

I'm running Alleg on Vista Ultimate 32bit. Steps I followed were...
1. Install Vista
2. Update Vista/Drivers
3. Install Allegiance and required updates. (VC++, .NET 1.1 etc)
4. Allow Allegiance in Windows Firewall.
5. Run ASGS in Admin mode <- (Only needed when theres an update to be downloaded/installed AND if you're using UAC)
6. Allow ASGS to update to latest version
7. Reallow Allegiance in Windows firewall as it had changed and was now being silently blocked.
8. Play

The only time I've seen symptons like yours is when my router wasn't configured quite right back pre-R3, so I would tend to be looking at that as the culprit.
I'd be tempted to do a factory reset on your router just to get it back to a clean slate.
Reconfigure your internet settings on it and turn off the firewall settings in it. Hopefully Allegiance will just work. If not make sure UPNP is off, from memory that was my issue. UPNP was mapping the ports when I connected to the lobby for the lobby server [only] which meant when I tried to connect to the servers the ports were essentially blocked.

Good Luck.

Arkof wrote:QUOTE (Arkof @ Nov 22 2007, 06:45 PM) As Ogo said, Get off the DMZ and remove your port forwarding rules.
Ignore DrB, You do not have to run ASGS in admin mode.
TE is a legend.

I'm running Alleg on Vista Ultimate 32bit. Steps I followed were...
1. Install Vista
2. Update Vista/Drivers
3. Install Allegiance and required updates. (VC++, .NET 1.1 etc)
4. Allow Allegiance in Windows Firewall.
5. Run ASGS in Admin mode <- (Only needed when theres an update to be downloaded/installed AND if you're using UAC)
6. Allow ASGS to update to latest version
7. Reallow Allegiance in Windows firewall as it had changed and was now being silently blocked.
8. Play

The only time I've seen symptons like yours is when my router wasn't configured quite right back pre-R3, so I would tend to be looking at that as the culprit.
I'd be tempted to do a factory reset on your router just to get it back to a clean slate.
Reconfigure your internet settings on it and turn off the firewall settings in it. Hopefully Allegiance will just work. If not make sure UPNP is off, from memory that was my issue. UPNP was mapping the ports when I connected to the lobby for the lobby server [only] which meant when I tried to connect to the servers the ports were essentially blocked.

Good Luck.

I recently installed that VC runtimes update that the devs aren't dealing with (understandable, all coding done is on their time). Regardless, if this community can't move forward with the times; then I'm done with it til it grows up with everything else.

Keep me updated if this gets fixed.

grinableanimal at hotmail.com is my msn.

Marking this as unsolved due to user stupidity in using Vista.

deceit wrote:QUOTE (deceit @ Nov 22 2007, 10:03 PM) I recently installed that VC runtimes update that the devs aren't dealing with (understandable, all coding done is on their time). Regardless, if this community can't move forward with the times; then I'm done with it til it grows up with everything else.

Keep me updated if this gets fixed.

grinableanimal at hotmail.com is my msn.

I'm not sure how else you would want the devs to deal with the missing files on your computer. They told you to install them. I'm sure if you asked, one would even be willing to Remote Desktop into your machine and install them for you. There really isn't much else they could have done.

And I'm puzzled at your comment about the community moving forward. The whole reason why those dlls are needed in the first place is because the community is moving forward and compiling the game against the latest compiler. The biggest update in R4 is one that you don't really see. KGJV rewrote a lot of the graphics calls to use newer libraries.

I mean... if you're going to take a cheap shot at our community, at least take a cheap shot.

Finally, back on topic... you asked the community for help in solving your "Failed to connect" problem.

When you log in, you connect to the ASGS lobby. This computer grabs a list of all the games running on all of the different servers, and shows them to you. When you try to join a game, your client attempts to connect to servers on whatever port that game-server is set up to run on. (By default I believe this is 2402, but it's been a while since I looked at the updates radar/Imago/KGJV/others made to the networking code in R3)
Since your client worked properly with your current Vista OS and your current router, and R4 is not working then as you say it's a problem with the update to R4. Also, since no networking code was changed in R4, the problem is unlikely to be your networking setup (routers, networking settings).

Looking at what is still possible, there's a pretty short list:Firewall is blocking access to the gameserverCould occur when it's "disabled"could occur when it's uninstalled (Norton Internet Security did this for a long time)Firewall rule became invalidated when Allegiance.exe was replacedSome other application is interfering with the communication between your computer and the gameserver on port 2402Since you can't think of any other programs that are interfering with Allegiance's comms, then it's only natural for people to suspect the 1st possibility, which pretty much everyone did in this thread. If you still can't identify it, try grabbing Wireshark and sniffing the packets between you and the gameserver to see what's up.

Anyways. Whether it's a misconfigured firewall or your lack of understanding with your shiny new OS, I'm done with it... unless you grow up like everyone else and learn how to use your firewall/OS, or learn how to use ask Helpline people for help without insulting them all in one (incorrect) blanket statement.

--TE