[THIN] Re: Cannot connect to 4.5 server externally

If it was the firewall ports I believe you get a message about there being no 
server on the specified subnet.  If it was the alternate IP address you get a 
message saying there was not alternate IP address found.  Everytime I have seen 
protocol driver error it has been network or routing.   If it is working via 
RDP then I would say your NAT is fine and you have a problem with the Alternate 
IP address.  Did you perhaps set the alternate IP address on the wrong NIC?

Chris

________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of 
Peterson David
Sent: April 28, 2009 3:11 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Cannot connect to 4.5 server externally

No errors in the server log, set to per user.

________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of 
Jeff Pitsch
Sent: Tuesday, April 28, 2009 2:24 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Cannot connect to 4.5 server externally
any errors in the event logs?
On Tue, Apr 28, 2009 at 12:25 PM, Peterson David 
<DPETERSO@xxxxxxxxxxx<mailto:DPETERSO@xxxxxxxxxxx>> wrote:
Altaddr is set, I also completely disabled the client firewall to make sure 
that wasn't causing an issue. I can connect to my 4.0 servers fine from the 
outside via the quick launch. Client version is 11.0.0.5357.

________________________________
From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> 
[mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf 
Of Jeff Pitsch
Sent: Tuesday, April 28, 2009 10:28 AM
To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Cannot connect to 4.5 server externally
is your NAT setup properly and your altaddr on the citrix box?  In program 
neighbhorhood did you configure your firewall button correctly?

Jeff Pitsch
On Tue, Apr 28, 2009 at 9:53 AM, Peterson David 
<DPETERSO@xxxxxxxxxxx<mailto:DPETERSO@xxxxxxxxxxx>> wrote:
We have a new 4.5 server in it's own farm, on server 2003. I can connect 
internally using a custom ICA connection or quick launch but cannot connect 
from the Internet (we don't have WI for this system installed yet.)

When I try to connect via Quick launch over the Internet I get a protocol 
driver error, from a custom ica connection I get XenApp server not available. 
Telnetting to port 1494 (get ICA) and 2598 work, as does connecting via rdp.

From inside the network I can connect via ICA fine, but only using the internal 
name. On our 4.0 servers, I can connect using either.

Anyone have any suggestions?


NOTICE: This electronic mail transmission from the law firm of Dinsmore & Shohl 
may constitute an attorney-client communication that is privileged at law. It 
is not intended for transmission to, or receipt by, any unauthorized persons. 
If you have received this electronic mail transmission in error, please delete 
it from your system without copying it, and notify the sender by reply e-mail, 
so that our address record can be corrected.



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Other related posts: