• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2363
  • Last Modified:

XenApp Web Interface altAddr not working on 1 server but on others

Ok, I know altaddr is bad.. I get it and will be adding CSG soon enough but...

I have a new XenApp server I added to the farm.

I configured WebInterface the same as my existing server (which works fine).

new server I login to WI fine, trying to launch app it says cant find server.  I downloaded the ICA file and in it shows the internal FQDN of my server for the address, on my other xenapp/wi box it shows the external ip in the file and that one works.

on the new one I set altaddr just like the other server (diff IP of course), made DEFAULT - ALTERNATE

cmd prompt tpy altaddr and it shows local and external...

why would it still sling the internal name instead othe external IP??????  I almost dont think its me or the config.  Only difference is I loaded WI5.4 instead of WI5.2 on this server... only difference.
0
dbllp
Asked:
dbllp
  • 8
  • 6
1 Solution
 
Zach2001Commented:
Are you using Citrix Secure Gateway ? - What version of Xenapp ?
I have found that before upgrading the web interface / secure gateway I have had to delete the alt addr, reboot, upgrade, then redo the alt addr.

Though, truth be told, since Xenapp 5, the web interface managment console is so good, I rarely use the altaddr command at all.

If I were you, I would altaddr /delete /v reinstall the WI and attempt configure via web interface.
0
 
dbllpAuthor Commented:
No gateway, Xenapp 5 on 2003x64 (so basically xenapp 4.5)

I installed WI before setting altaddr so I dont think its that.
0
 
Zach2001Commented:
I take it the machine is not multihomed and is a single nic single IP connecting via NAT / port forwarding firewall.

have you ran altaddr /delete <internalIPAddress>  to remove the internal IP ?
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
dbllpAuthor Commented:
correct

I have one that works fine but its old so I want to replace it with this machine but this is holding me up.

altaddr is set, the web interface is DEFAULT-ALTERNATE, but I used firefox to save the ICA file it creates when connecting and it contains the internal host name.  If I launch from my existing the ICA file contains the external IP like it should.  Not sure why this machine is not using the ALT even though it is configured to do so.  Old machine is 32bit new one is 64 bit, other than that not much difference.  Same versions of Windows, same version of XenApp, same hotfixes/rollups... etc... I cant get the new one to use the alt address.

0
 
Zach2001Commented:
in the OP you mention internal *name* - do you mean IP ?  If using the name, this would use internal reverse DNS to find IP...

So running  altaddr /delete <internalIPAddress> returns no errors
but running altaddr displays both internal & external IP's ?
0
 
dbllpAuthor Commented:
it is using name, yes.  and no errors with delete on the alt.  and yes, it shows:

local             alternate
default         xx.xx.xx.xx (external IP)

looks JUST like the one that is working.
0
 
dbllpAuthor Commented:
sorry to be clear... it is using the name NOT IP in the ICA file on the non working server. - not sure why.

0
 
Zach2001Commented:
ok; It sounds to me like the client address map has been configured and you are either accessing the citrix machine from a subnet it thinks is local or the address map has been configured so that * is local.

This should be very easy to spot and rectify within the GUI, though there may still be an nfuse.conf knocking about on the newer WI.

I suppose it may be worthwhile going into the GUI under web interface, uninstalling / reinstalling the site, or at the very least, repair the site - I think think would redo the client address map.
0
 
dbllpAuthor Commented:
thanks, tried that - repairing, deleting, creating new.. .etc... I restart the IMA after each attempt.  I even went as far as deleting the site in IIS and creating a new one.
0
 
Zach2001Commented:
Very weird, in that case, if I were you, I would locate the webinterface.conf and conpare it against http://support.citrix.com/proddocs/index.jsp?topic=/web-interface-impington/wi-webinterface-conf-parameters-gransden.html
paying attention to addressresolution type and alternate address parameters.

You are downloading the ICA file from a browser well outside your network, arn't you ?
0
 
dbllpAuthor Commented:
ok... you da man.

For whatever reason when it creates the CONF file its not right... so what I did is take the CONF file from my existing working server, did a find and replace to update new server's name and IP address and BAM! its working.

Now why it wont make the correct conf file I dont know.  Here are the differences I can see:

working file:
ClientAddressMap is #'d out so its not using it
nonworking file:
ClientAddressMap ={internal IP}/255.255.255.0,Normal,*,Alternate

working file:
Farm1 is #'d out
nonworking file:
Farm1 info is populated

working file:
ServerAddressMap=[internal IP]:1494, [external IP]:149
nonworking file:
ServerAddressMap is #'d out so not in use

I did notice the WI VERSION is 5.2.0.36 on my old server and 5.3.0.0 on the new one and the CONF file is bigger (more lines) on the old one.

Instead of modifying I just used the CONF from the old server with current server info.

I wish I knew why it wasnt updating/creating the conf file properly to begin with though.
0
 
dbllpAuthor Commented:
also:

AddressResolutionType=dns-port is active in the non working and # on the working

most of the AllowCustom stuff is # on the working and active on the non working.

too much to list but a LOT of stuff is # on the working and not on the non-working...
0
 
dbllpAuthor Commented:
Got me working... now to figure out the WHY behind it.
0
 
Zach2001Commented:
Well, thank goodness for that, I though *I* was going mad, goodness knows how you were doing ;)

I would have thought that info would have been populated from the XML service - so should obviously be the same within each zone - in which case I would blame farm connectivity... but I truly don't know enough about the ins and outs of where that file get's it's initial paramters from, it used to just be a copy from conf.default...

Perhaps one for Citrix support themselves, now that the urgency has passed - worth adding to my KB though!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now