Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Citrix Systems (CTXS) -- Ignore unavailable to you. Want to Upgrade?

To: MikeM54321 who wrote (6625)	5/28/1999 4:44:00 PM
From: Bill Tessaro	Respond to of 9068

Re ICA port : I believe it is 1494 Re FW issues : Check the Citrix WWW site for both F/W and (I believe) some demo/web-enabling-your-applications whitepapers. Due to various client/printer/clipboard/etc. being "mapped" across the respective ICA virtual channels, the Server side can restrict this. Often for demo purposes it is so people don't play games with the demo server by writing huge files, etc. At the same time applications don't have to be "written" to run on WinFrame/MetaFrame, decently done Windows applications should have no problems. Bill

To: MikeM54321 who wrote (6625)	5/28/1999 4:52:00 PM
From: Scott Overholser	Respond to of 9068

yes - once the firewall configuration change is made it is done for good. of course, it can be changed back to not allow ica at a later time. i am not a metaframe expert but from a general tcp/ip traffic perspective there is nothing particular to the given application layer software that affects operation through a firewall. my employer publishes an open ports list on a webpage. adding new ports to the open ports list is as simple as making the request along with justification. i don't think the justification bar is very high because as i look at the list now i see microsoft's internet gaming zone, icq, compuserve, cuseeme, etc... last -but not least- citrix winframe is open on port 1494 and citrix webclient on port 49160. i have never tried using the open ports for citrix products - never looked before. i'm gonna try it out. i'll post the results. i have built many firewalls and am most intimately familiar with their principles of operation. basically, anything that uses tcp can be passed through a firewall. it is a non-issue from citrix's point of view. it's no different than passing http. -- But once he does this, does that mean the user/client can use Citrix from then on out? In other words, is there anything else in MetaFrame that prevents it from EASILY working through a firewall once you overcome the initial barrier?