Free Allegiance Forums

I just installed and everything, so I'll simply say everything I think might be relevant.

1. Installed, perfectly fine.
2. Run the file, attempt to log in, I get the following error "Connectivity Failure, Check your internet connetion"

My system is as follows.

Windows Version (and Service Packs): Windows 7 Ultimate 64-bit (6.1 build 7600)
Processor Speed: Intel® Core™2 Duo CPU T7500 @2.20 GHz (2CPUs)
RAM: 3072MB
Connection Type (Dialup, Cable, DSL, other): PROXY SERVER BASED
Modem (Make and Model#): I don't know.
Router (Make and Model#): I don't know.
Internet Service Provider(company name): ISP is studentenwerk Mannheim's free internet...
Location(State/Province/Locality, and Country): Germany, Mannheim.

I don't see anyway to change the connection to go through the HTTP PROXY... help?

EDIT: Here is the diagnostics copy and paste section. Anyone know what is going on?


ALL_HTTP: HTTP_CACHE_CONTROL:max-age=259200
HTTP_CONNECTION:keep-alive
HTTP_VIA:1.1 www-cache.uni-mannheim.de:3128 (squid/2.7.STABLE6)
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=yystee45pqqmcd55g4j2fiqv
HTTP_HOST:asgs.alleg.net
HTTP_USER_AGENT:Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7
HTTP_X_FORWARDED_FOR:10.19.2.59

ALL_RAW: Cache-Control: max-age=259200
Connection: keep-alive
Via: 1.1 www-cache.uni-mannheim.de:3128 (squid/2.7.STABLE6)
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=yystee45pqqmcd55g4j2fiqv
Host: asgs.alleg.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7
X-Forwarded-For: 10.19.2.59

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.99.71
REMOTE_HOST: 134.155.99.71
REMOTE_PORT: 47881
REQUEST_METHOD: GET
SCRIPT_NAME: /asgsweb/diagnostics.aspx
SERVER_NAME: asgs.alleg.net
SERVER_PORT: 80
SERVER_PORT_SECURE: 0
SERVER_PROTOCOL: HTTP/1.0
SERVER_SOFTWARE: Microsoft-IIS/6.0
URL: /asgsweb/diagnostics.aspx
HTTP_CACHE_CONTROL: max-age=259200
HTTP_CONNECTION: keep-alive
HTTP_VIA: 1.1 www-cache.uni-mannheim.de:3128 (squid/2.7.STABLE6)
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=yystee45pqqmcd55g4j2fiqv
HTTP_HOST: asgs.alleg.net
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7
HTTP_X_FORWARDED_FOR: 10.19.2.59

ASGS can run behind a proxyserver, but Allegiance needs direct access to the

Du brauchst einen richtigen Zugang zum Internet (also nicht ueber Internetproxy des Intrsnets).

PS:
ASGS uses proxysettings of IE.

There is a setting called "Connection Port" in the ASGS window's ASGS pull down menu, try
changing that.

If that fails, could you please post results of a trace to asgs.alleg.net?

To perform a trace:
1. Press Windows_Key+R, a white window will appear.
2. Type "cmd" without the parenthesis (") into the white window, press Enter, a black window will appear.
3. Type "tracert asgs.alleg.net" without the parenthesis ("), press Enter, wait for the command to complete.
4. Right click the black window, select "Select" option (I have no idea what it's called in German version of Windows, but it'll be something similar).
5. Drag a box around the result of the trace command, press Enter when done - this will copy the selected text to your clipboard.
6. Create a new post in this thread and paste the result into it.

pkk wrote:QUOTE (pkk @ Nov 3 2010, 03:43 PM) ASGS can run behind a proxyserver, but Allegiance needs direct access to the

Du brauchst einen richtigen Zugang zum Internet (also nicht ueber Internetproxy des Intrsnets).

PS:
ASGS uses proxysettings of IE.

Which is it? ASGS can run behind a proxyserver, or a proxyserver isnt a correct path to the internet?

ogorass wrote:QUOTE (ogorass @ Nov 3 2010, 03:45 PM) There is a setting called "Connection Port" in the ASGS window's ASGS pull down menu, try
changing that.

If that fails, could you please post results of a trace to asgs.alleg.net?

To perform a trace:
1. Press Windows_Key+R, a white window will appear.
2. Type "cmd" without the parenthesis (") into the white window, press Enter, a black window will appear.
3. Type "tracert asgs.alleg.net" without the parenthesis ("), press Enter, wait for the command to complete.
4. Right click the black window, select "Select" option (I have no idea what it's called in German version of Windows, but it'll be something similar).
5. Drag a box around the result of the trace command, press Enter when done - this will copy the selected text to your clipboard.
6. Create a new post in this thread and paste the result into it.

Here is the little log built into the ASGS client for both direct and HTTP play.
• Checking connectivity
• Using Port: DirectPlay
• Connectivity failure. Check your internet connection.
• The request failed with HTTP status 417: Expectation failed.
• 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.

And here is the lovely trace route. (it is still going and timing out at each one...)

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
this continues until hop 30...

Can't ping it either.

Wyrsa wrote:QUOTE (Wyrsa @ Nov 3 2010, 03:46 PM) Which is it? ASGS can run behind a proxyserver, or a proxyserver isnt a correct path to the internet?

Das Internet besteht nicht nur aus dem Http Protokoll, wofür der Proxy nunmal dient.

Wenn dein Rechner nur über den Proxy ins Internet kommt, brauchst du nicht weiter zu testen und zu probieren.

Öffne einfach einmal die Eingabeaufforderung und gib „ping asgs.alleg.net“ ein.

Wenn es funktioniert, habe ich unrecht.

pkk wrote:QUOTE (pkk @ Nov 3 2010, 03:53 PM) Das Internet besteht nicht nur aus dem Http Protokoll, wofür der Proxy nunmal dient.

Wenn dein Rechner nur über den Proxy ins Internet kommt, brauchst du nicht weiter zu testen und zu probieren.

Öffne einfach einmal die Eingabeaufforderung und gib „ping asgs.alleg.net“ ein.

Wenn es funktioniert, habe ich unrecht.

I can't ping asgs.alleg.net it times out.

Das hier sollte dir weiterhelfen:
http://ncc.uni-mannheim.de/index.php?id1=193&id2=199

pkk wrote:QUOTE (pkk @ Nov 3 2010, 04:09 PM) Das hier sollte dir weiterhelfen:
http://ncc.uni-mannheim.de/index.php?id1=193&id2=199

Oh yea... the VPN client... I bet everything will be fine after that. If not I will post again here.

pkk, it would be much easier to keep track of what's going on here if you could stick to English