Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NFuse problems

Status
Not open for further replies.

buddyel

MIS
Mar 3, 2002
279
US
We are in the process of moving our web server from the internal network to our DMZ. When I pull up the NFuse page when I am locally connected or connected via our VPN Client everything works great. However if I try to connect via an outside machine I can get the published application listing but if I try to run an app I get the following error:

"Cannot connect to the Citrix Metaframe server.
There is no Citrix MetaFrame server configured on the specified address."

Anyway have any suggestions? Thanks in advance.
 
Let's say the internal adres on the nic of your server is 192.168.0.1
That way NFuse will work after a default installation, if your clients are running 192.168.0.x
Of course when connecting over the internet, a user at home will not get much respons from 192.168.0.1

Ok, so here we go: i asume you've enabled port 1494 for citrix traffic, and port 80 for NFuse traffic, running through your firewall's public ip to the citrix server. Whether residing on the DMZ, or the local LAN.
Now let's say, your public ip is 123.123.123.1

On the citrix server you need to run a command, to tell the server to respond with it's public adres, if needed.
In cmd run: altaddr /set 123.123.123.1
(reboot server for settings to take effect)

On the firewall, make sure the following rules are open:
(i am asuming the citrix/nfuse is in the DMZ)
allow port 1494 wan to DMZ inbound, and high ports (1023 - 5000) outbound
allow port 80 wan to DMZ in and outbound

On the NFuse server either configure the alternative adres use in the admin page, or make sure the below 2 sample lines are in the nfuse.conf (needs an iis reset if changed outside the admin page)

AlternateAddress=Mapped
ClientAddressMap=192.168.0.,Normal,*,Alternate

After these changes, the template will get filled with the alternate adres for internet users, and the internal adres for your lan users.

Stefan
 
I have made the changes you suggested and I still get the same results.
 
Also have you tried connecting via the client as opposed to Nfuse, just for trouble shooting purposes?

Try using the client (remember to enable the alternate firewall address for firewall connections). If you are able to fire up an app, then it's the way you have set up Nfuse. If you can't then it has to be either ica packets are not getting thru on port 1494 or how you have set up alternate address on the servers on the farm, and last but no least you could have a dodgy citrix client on your pc (have had that before).

Regards
Roy

 
Just so we are on the same page...our metaframe server is on our internal LAN and the NFuse IIS page is on our DMZ Web servers.

Currently we run NFuse15 on our internal web server which is configured for the same citrix server we are trying to get working on the dmz. There is no altaddr set on the citrix server currently.
 
also,

the internal address of the citrix is 10.1.1.16. I checked the configuration of the existing NFuse15 and it shows the citrix server being configured using its public ip of x.x.x.16.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top