Has anyone ever recieved this citrix error before. Cannot connect to citrix metaframe server there is no citrix metaframe server configured on the specified address. I'm running the latest version of nfuse on windows server 2003 enterprise edition. The metaframe xp feature release 3 is on a windows 2000 advanced server box. I've forwared port tcp port 1494 to the 2003 box thats running nfuse. I recieved this error when connecting from a laptop running windows me. I have port 1494 forwarded to the citrix server and ports 80 and 443 going to the nfuse server. Can someone please help me fix this problem.
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!
metaframe xp can't connect over web 2
- Thread starter alpha88
- Start date
-
2
- #2
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.
Free citrixprinting support
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.
Free citrixprinting support
- Thread starter
- #3
xs4citrix I'm testing this citrix box behind a regular linksys befsr41 home router so I'm actually fowarding incomeng request to the servers. It will latter be deployed on a client site where they do have a firewall with a dmz. Can you tell me how does what I want to do come into play with a regular home router that has a public ip address that changes from time to time. Also how do I edit the nfuse conf file directly I mean what do I use to open it I'm assuming its more simple to edit the file directly the nfuse web interface is confsing to me. Maybe thats because I'm new to citrix.
Basicly it's the same setup, but if the router get different ip's it's not possible. (or only for a short time, as you hardcode the public ip as an alternate adres on the citrix server)
Free citrixprinting support
Free citrixprinting support
- Thread starter
- #5
xs4citrix theres no way to use a dynamic dns service with this. Also some home routers come with a dynamic dns option I think I say an option for that in a netgear that I also have. Because right now I run an exchange 2003 server and a iis 6.0 web server and thats how I keep them up is dymanic dns. I basically use zonedit.com for dns resoultion this service works great with dynamic dns I than load a dynamic dns cleint on one of my server boxes and it updates my ip whenever it changes. Theres got to be a way to to that with citrix.
- Thread starter
- #6
I wish they had an edit option if so I could add this to my last reply, but anyway is there an option in there where you can set a dns record for example. I have a dns record created thats citrix.stephensnetworks.com. citrix.stephensnetworks.com is an a record thats mapped to my dynamic dns software and automatically updates the dns zone for me at zonedit.com this would of course allow me to always have a current public ip address.
Your problem is not DNS resolution. It is the hardcoding of the altaddr adres on the server.
You cannot change that behaviour. There are only workarounds left, like using CSG, or multiple NFuse sites.
Only the ability for running 1 NFuse site for internal and external access is lost.
Free citrixprinting support
You cannot change that behaviour. There are only workarounds left, like using CSG, or multiple NFuse sites.
Only the ability for running 1 NFuse site for internal and external access is lost.
Free citrixprinting support
- Thread starter
- #8
xs4citrix I would like to ask you whats the deal with all this altaddr? This program is exremely different in the way it behaves for internet use. Also I do have csg how will this product solve my problem. I'm sorry if I ask stupid questions. I just ordered a few citrix books should have them by Tuesday.Is this csg something like a proxy so in realty they will connect to the proxy and not directly the nfuse site.
If you read my initial story, you can tell the behaviour of altaddr.
Simply said, if the real server ip is 192.168.0.1 then it will always respond with that adres.
So if mapped through a firewall, it will still say it's the 192 adres, regardless of the connection method.
The altaddr trick gives the citrix server an option to respond with it's own adres, or it's alternative adres. Nothing more, nothing less.
The CSG is a gateway between the citrix server and the client. Since it's pure DNS FQDN driven, i think you can use the setup you have in mind.
As a small test, i altered the template.ica file from an NFuse setup, to match FQDN, without using an altaddr.
I used the following lines:
[WFClient]
Version=2
HttpBrowserAddress=citrix.domain.com
TcpBrowserAddress1=citrix.domain.com
[ApplicationServers]
sample=
[sample]
Address=citrix.domain.com
InitialProgram=#Desktop
ClientAudio=Off
Compress=On
ScreenPercent=100
DesiredColor=4
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
If your internal DNS resolution, matches the local adres of the server, and externally, you use the fqdn DNS trick you had in mind, in theory it could work with your current setup.
Free citrixprinting support
Simply said, if the real server ip is 192.168.0.1 then it will always respond with that adres.
So if mapped through a firewall, it will still say it's the 192 adres, regardless of the connection method.
The altaddr trick gives the citrix server an option to respond with it's own adres, or it's alternative adres. Nothing more, nothing less.
The CSG is a gateway between the citrix server and the client. Since it's pure DNS FQDN driven, i think you can use the setup you have in mind.
As a small test, i altered the template.ica file from an NFuse setup, to match FQDN, without using an altaddr.
I used the following lines:
[WFClient]
Version=2
HttpBrowserAddress=citrix.domain.com
TcpBrowserAddress1=citrix.domain.com
[ApplicationServers]
sample=
[sample]
Address=citrix.domain.com
InitialProgram=#Desktop
ClientAudio=Off
Compress=On
ScreenPercent=100
DesiredColor=4
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
If your internal DNS resolution, matches the local adres of the server, and externally, you use the fqdn DNS trick you had in mind, in theory it could work with your current setup.
Free citrixprinting support
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question