Connectivity failure.

notjarvis · Post by **notjarvis** » Tue Mar 30, 2010 5:02 pm

You could just uninstall the AV, reboot, and try to connect to the game.

Virus Danger should be minimal if you just do this - would confirm whether it's worth changing AV.

I use Avira on 32 bit XP happily, though I haven't updated to their newly released version yet...

KaiserCross · Post by **KaiserCross** » Tue Mar 30, 2010 5:07 pm

I think that's worth a try.

brb

KaiserCross · Post by **KaiserCross** » Tue Mar 30, 2010 5:29 pm

Well I downloaded the Avira installer again before uninstalling it. But when I went to reinstall it gave me some trouble. First it told me to disable windows defender, then it told me the installation failed, then it told me the installation was successful, but that I couldn't turn it on. Seemed strange. So basically now I have AVG, and I made sure I didn't install the firewall component.

However the really important thing is: I received the exact same error even with my antivirus uninstalled.

fuzzylunkin1 · Post by **fuzzylunkin1** » Tue Mar 30, 2010 5:46 pm

It actually looks like it may be a problem with .NET services. I see you had problems with Windows Update . . . you should try to resolve that no matter what to receive important security updates from Microsoft and various .NET updates.

Perhaps the issues are related, not sure.

After a quick search for 80072EFD, came up with these links:

http://social.answers.microsoft.com/Forums...75-82d815fa9a8f
http://windows.microsoft.com/en-us/windows...-error-80072efd

ogorass · Post by **ogorass** » Tue Mar 30, 2010 6:50 pm

Seems like we can rule out the AV now - AVG Free (the one without the firewall) has no issues with Allegiance.
Read up on what fuzzy suggested.
Also, can you do a tracert to 'asgs.alleg.net'? If you don't know how, post here, I'll walk you through it.

KaiserCross · Post by **KaiserCross** » Wed Mar 31, 2010 12:59 pm

Yeah I looked through the links fuzzylunkin1 posted and tried all the things listed on the microsoft help page. Most of it was just antivirus and firewall stuff, which I'd already tested. I looked at the hosts file and removed proxies, it all seemed fine. And changed nothing. (That was when I decided after 3 hours of attempted problem solving it was time to sleep on it and re-tackle it the next day.)

I ran a tracert (after looking up what it was) and ended up with this:

Sorry that some of the lines wrap around, I didn't notice until it was already uploaded.

ogorass · Post by **ogorass** » Wed Mar 31, 2010 1:38 pm

The trace looks OK, so we can rule out some issue between you and the server.
This leaves us with some problem on your side... Something is not allowing ASGS to create an outbound connection to the server or even to create a socket. Might be .NET 2.0 issue. Try removing it, reinstalling and applying all the patches to it you can find on Windows Update (may require a couple of rounds of updating, keep checking WU after each update installs for any new ones that may appear).

Also, sorry for not typing out the usual walkthrough for tracert, I was at work and had to be quick about the post...

notjarvis · Post by **notjarvis** » Wed Mar 31, 2010 1:38 pm

Hmm, have you ever had Norton installed on this machine?

If so you may need to run their Norton Removal Tool, you can google it pretty easy I think....

remember to reboot before trying to connect....

KaiserCross · Post by **KaiserCross** » Wed Mar 31, 2010 3:38 pm

I did have norton, but I completely removed it (With the removal tool) so I could play allegiance. I also had to get NET 2.0.

I'm beginning to think that this problem really is coming from my problem with windows update, I'm probably just missing some patch for NET 2.0 or something. I'll try to see if I can get it again, see what happens. Although fuzzy is right, I should really get that fixed somehow even if I can get allegiance to run again.

EDIT: How do I uninstall NET 2.0 before reinstalling it?

Post by **FreeBeer** » Wed Mar 31, 2010 4:25 pm

You should be able to do so through Add/Remove Programs.