Page 1 of 1

Posted: Tue Nov 09, 2010 1:09 pm
by LunarAvenger
I get this log when trying to sign in with Allegiance.

• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: HTTP
• Connectivity failure. Check your internet connection.
• The request failed with HTTP status 417: Expectation failed.

So I tried it with DirectPlay.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Connectivity failure. Check your internet connection.
• The request failed with HTTP status 417: Expectation failed.

All I want to do is play with everyone else... :(

Posted: Tue Nov 09, 2010 1:33 pm
by FreeBeer
That's a new one on me. A quick Google for the error hasn't been too helpful, but in some cases it is related to using a proxy server. Are you connecting through a proxy?

Posted: Tue Nov 09, 2010 1:42 pm
by LunarAvenger
FreeBeer wrote:QUOTE (FreeBeer @ Nov 9 2010, 02:33 PM) That's a new one on me. A quick Google for the error hasn't been too helpful, but in some cases it is related to using a proxy server. Are you connecting through a proxy?
Previously yes, however I just got the credentials for my VPN and shouldnt be going through a proxy server anymore. :S

EDIT: here is the new diagnostic log.


ALL_HTTP: HTTP_CONNECTION:keep-alive
HTTP_ACCEPT:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
HTTP_ACCEPT_CHARSET:ISO-8859-1,utf-8;q=0.7,*;q=0.3
HTTP_ACCEPT_ENCODING:gzip,deflate,sdch
HTTP_ACCEPT_LANGUAGE:en-US,en;q=0.8
HTTP_COOKIE:ASP.NET_SessionId=i4jovvudi1g5ogbzi32vrv55
HTTP_HOST:asgs.alleg.net:2369
HTTP_USER_AGENT:Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7

ALL_RAW: Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Cookie: ASP.NET_SessionId=i4jovvudi1g5ogbzi32vrv55
Host: asgs.alleg.net:2369
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7

APPL_MD_PATH: /LM/W3SVC/1944922576/Root/ASGSWeb
APPL_PHYSICAL_PATH: D:\Web\ASGSroot\ASGSWeb\
AUTH_TYPE:
AUTH_USER:
AUTH_PASSWORD:
LOGON_USER:
REMOTE_USER:
CONTENT_LENGTH: 0
CONTENT_TYPE:
GATEWAY_INTERFACE: CGI/1.1
INSTANCE_ID: 1944922576
INSTANCE_META_PATH: /LM/W3SVC/1944922576
LOCAL_ADDR: 204.14.17.25
PATH_INFO: /asgsweb/diagnostics.aspx
PATH_TRANSLATED: D:\Web\ASGSroot\ASGSWeb\diagnostics.aspx
QUERY_STRING:
REMOTE_ADDR: 134.155.149.97
REMOTE_HOST: 134.155.149.97
REMOTE_PORT: 56382
REQUEST_METHOD: GET
SCRIPT_NAME: /asgsweb/diagnostics.aspx
SERVER_NAME: asgs.alleg.net
SERVER_PORT: 2369
SERVER_PORT_SECURE: 0
SERVER_PROTOCOL: HTTP/1.1
SERVER_SOFTWARE: Microsoft-IIS/6.0
URL: /asgsweb/diagnostics.aspx
HTTP_CONNECTION: keep-alive
HTTP_ACCEPT: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.3
HTTP_ACCEPT_ENCODING: gzip,deflate,sdch
HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.8
HTTP_COOKIE: ASP.NET_SessionId=i4jovvudi1g5ogbzi32vrv55
HTTP_HOST: asgs.alleg.net:2369
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7

Posted: Tue Nov 09, 2010 2:04 pm
by FreeBeer
I've never played with a VPN, and there's nothing I can do to replicate what you have on your end. But you might want to do a little bit of research since it's likely to have creeped up elsewhere: Allegiance uses the same communications as other Microsoft Games (of its era at any rate), so if someone's managed to get through to, say, Age of Empires, the same techniques should work for Allegiance.

Posted: Tue Nov 09, 2010 6:39 pm
by LunarAvenger
FreeBeer wrote:QUOTE (FreeBeer @ Nov 9 2010, 03:04 PM) I've never played with a VPN, and there's nothing I can do to replicate what you have on your end. But you might want to do a little bit of research since it's likely to have creeped up elsewhere: Allegiance uses the same communications as other Microsoft Games (of its era at any rate), so if someone's managed to get through to, say, Age of Empires, the same techniques should work for Allegiance.
It is the 417 error that is bugging me. I don't understand that error.

Anyways, my VPN changes nothing except makes it seem like on my machine nothing is going through a proxy. (cute huh?)

So things like outlook would work now... but I don't care about outlook.

I'll keep you all updated. I really want to play bad, even though I've never played before.

Posted: Tue Nov 09, 2010 6:43 pm
by fuzzylunkin1
In ASGS go to "ASGS->Connection Port" and say what you have clicked. I personally have never seen it work through HTTP and have always needed to used DirectPlay.

EDIT:
Oh wait you're the guy from the other topic . . . :unsure: .

EDIT 2:
Try to give proxy settings to Internet Explorer, as that's what Allegiance uses.