[Vovan27]

странно конечно но проблема ушла также как и появилась, но интересно было бы узнать неужели неукого такой проблемы не было

[Butunin Klim]

Цитата

Internal LAN For instance you internal IP range is 192.168.x.x With a default installation of the Web Interface (NFuse) it will work for you LAN Clients. Of course, when connecting over the Internet, a home User will NOT get any response from 192.168.x.x Set the Public IP for the Citrix MetaFrame Servers Whether residing on the DMZ, or the local LAN. Let's also say, the Public IP is 123.123.123.1 On the Citrix Servers you need to run the altaddr command, to tell the servers to respond with the Public address, if needed. On the command line run: altaddr /set 123.123.123.1 FireWall Settings for Citrix & Web Interface Asuming Citrix MetaFrame/Web Interface are in the DMZ, enable following rules: - Allow TCP Port 1494 WAN to DMZ inbound (Citrix ICA) - Allow high TCP Ports (1023 - 5000) outbound (Citrix ICA) - Allow TCP Port 80 WAN to DMZ In- and outbound (HTTP) (Check FW from outside with: "Telnet 123.123.123.1 1494" and "Telnet 123.123.123.1 80") Web Interface NAT Configuration On the Web Interface Server either configure: A: The alternative address use in the admin page http://<WI-Server>/Citrix/MetaFrameXP/WIAdmin/ Don't forget to SAVE and APPLY Settings or B: Make sure the two sample lines below are in the NFuse.conf (needs an IIS reset if changed outside the WI admin page, run IISRESET on the command line) AlternateAddress=Mapped ClientAddressMap=192.168.0.,Normal,*,Alternate (Don't forget the last dot in the local IP range!) After these changes, the template will get filled with the alternate address for Internet users, and the internal address for your LAN Clients. Configuring NFuse 1.x for Use with Network Address Translation (NAT) CTX584485 Back to the Index

[Vovan27]

Все проблема решена, как выяснилось она связана была с моим постом по поводу DHCP