Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 610
  • Last Modified:

Problems with xenApp6.5, Storefront2.0 and netScaler Gateway

Hi,
I have some mysterious problems within my POC environment.

my installation:
1 NetScaler Gateway
1 Storefront2.0
1 Desktop Controller (XD7 + XA7)
1 XenApp Server Farm (3Server)

I have created 2 stores, one for XenApp7/XenDesktop7 (StoreXD7) and a second store for the old XenAoo6.5 Farm (StoreXA65).
I can connect from external to booth stores (and the applications) without any problems.
From within the LAN I can connect to the StoreXD7 without problems.
But if i try to open a connection to the application from the StoreXA65 the client tries to connect with TCP2598 (and afterwards TCP1494) to the NetScaler-Gateway Virtual Server IP and sometimes to the NetScaler SubnetIP.

some ideas??
Thanks in advance!
0
Dirk Kotte
Asked:
Dirk Kotte
  • 3
1 Solution
 
Sekar ChinnakannuSenior EngineerCommented:
did you configured the proper router to access the environment from outside of your network? if not give a try and check with network side
0
 
Dirk KotteSEAuthor Commented:
I think so...
and I have no problems accessing the environment from outside.
only if the client and storefront and xa6.5 server are within the same LAN (the netscaler is in one arm mode at the DMZ) I have the problems.

I don`t know, how the session is initiated ...
I think if the internal beacon-point is accessible the client should connects directly to the XA-server
0
 
NetminderCommented:
dkotte,

I changed the Topic Areas for this question from

--Citrix
--Remote Access Software

to
--Citrix
--Remote Access Software
--Virtualization
--Virtual Private Networking (VPN)

Netminder
Senior Admin
http://www.experts-exchange.com/R_26841.html
0
 
Dirk KotteSEAuthor Commented:
Storefornt and NS-Ag can't work with "altaddr".
if I configure a alternate address and allow the alternate-address within the web.config file the system use the alternate address for all connections - also the internal ICA-direct connections.

Workaround: disabled the internal beacon point and all connections (internal and external) use NS-GW and SSL.
0
 
Dirk KotteSEAuthor Commented:
my own solution works
0
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now