Port 1494

[Blutch]

I have W2K3 with NFuse installed behind DSL router and firewall. NFuse connects to my metaframe servers in my LAN. Port 1494 is open on router and firewall. When I connect to the Nfuse website from outside the office I can login and see my published applications. However when I want to start up an application I get the error 'No Metaframe server found on that address'

My guess is that port 1494 is closed on the NFuse server. I have tried everything but I don't seem to get that port open.

Any ideas?

 

[ascotta]

You need to set an ALTADDR on the citrix server to an outside the firewall address.

If your internal Metaframe is eg 192.168.1.10

and your router is 213. whatever you want run the following command from the dos prompt.

ALTADDR /SET 213. whatever you may need to reboot.
Then in your nfuse admin tell it to connect to the Alternative Address.

Cheers
Scott

 

[Blutch]

How do I put this in NFuse Admin.

In Server-Side firewall do I have to add (in the second option - alternate address) both the normal address and the alternate address ???

Thx for the advice

 

[ascotta]

I think in the server side firewall you want to tick the Use Alternate address.

This should force the connection to look for the Alternate address of the Citrix servers.


Cheers
Scott

 

[ascotta]

Sorry I should have explained better.


On the nfuseadmin web site go to server side firewall and check the Alternate Address radio button & save & apply.


Cheers
Scott




Cheers
Scott

 

[Blutch]

So for no mistakes.

In NFuse Admin - Server-side firewall
In Default Address Translation I check Alternate address

In Specific Address Translation settings I put the IP of the public address as alternate and check Alternate address also ??
Must I add my normal IP there also?

In Metaframe server address translation map I put nothing?

Is this it.

Thx for the advice

 

[ascotta]

Not quite.

In default address translation you do the tick.

Nothing in specific address translation.

on metaframe servers at dos prompt

ALTADDR /SET <external ip Address>

That should be it.


Cheers
Scott

 

[Blutch]

Now I don't understand anymore.

I can't specify an alternate ip address in the default address translation setting in nfuseadmin? Or isn't this necessary ???

I will try your suggestion and leave a message

Thx

 

[ascotta]

Don't worry bud I was having a foggy day yesterda.

You don't need to specify an Alternat address in nfuse admin.
It is really clever stuff (Allegedly).

Cheers
Scott

Cheers
Scott

 

[Blutch]

I did this, but I still can't get an application working.

I still get the error that there are no Citrix Metaframe servers on that address fount.

It is the ip of the router that I have to place as alternate address???

 

[ascotta]

In the one I have just set up.

I have the altaddr = external address of router.

My router has a rule sending any ica traffic to my citrix servers.

therfore

ALTADDR /SET <ip of router>

In the nfuse admin site I set the Default Address translations to &quot;Alternate Address&quot; radio box.

Specific address translation settings set at normal.

I have my XML running on port 80.

This works.

On my router I have a service for ICA and let anything on 1494 through and pointed at my internal metaframe boxes.

If you want security you had better get some certificates and use Secure gateway and Secure Ticket authority running too. But hey best to make sure you can connect normally first.

Cheers
Scott

 

[Blutch]

How did you setup the rule on your router to your Citrix servers?

 

[ascotta]

Its a itsy bitsy netgear router for a braodband connection.
I created the service for port 1494.

And said to the router via the GUI that anything on port 1494 is allowed in and out and point it to my internal addresss of Citrix boxes. I think that the pointing is superfluous (Spelling ?) It was the service creation in and out that does the trick methinks.

Cheers
Scott

 

[Ogi]

The Alternate Address is an address that you give each Citrix Server.

I give all mine:-

10.111.222.50
10.111.222.51
10.111.222.52
10.111.222.53
10.111.222.54

I also give a route for all 10.111.0.0 traffic to go to 192.168.4.1 which is my external router.

Once you've set this up when Citrix talks to clients on the outside of your network, Citrix replaces the IP address in the packets so that it goes out externally with it's NAT'ed address.

Cheers,
Carl.

 

[Blutch]

So you set up the route on the router itself to point all 10.111.0.0 traffic to 192.168.4.1?

 

[scjlin]

This is what i have in my configuration. I mapped the NAT table on my router for citrix metaframe. I mapped the local ip to public ip with static nat command. Then in my metaframe server i use ALTADDR /SET to setup my alternative default address to PUBLIC ip address.

Hope this work for your case.


sl