New Boundary Support Forum
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Dual Channel subscriptionExpand / Collapse
Author
Message
Posted 7/6/2005 11:55:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 7/8/2005 6:54:00 AM
Posts: 2, Visits: 1

Good day,

I need to subscribe to a channel that has access from a public IP and private IP. Basically the same channel name but two different IP's.  This is necessary due to firewall rules preventing access to to the public IP for computers inside my network.  I cannot alter the firewall's rules.

Being able to do this would allow me to maintain one Windows image that will work reguardless of its location (Intranet/Internet). What is the best method.....

Thank you,

 

Sgt Harvey

 



Sgt Harvey

RCSU(A)

Post #959
Posted 7/7/2005 11:56:00 AM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800

If you only want to have one image for both your internal and external systems, you would have to install IIS (or another web server) on your Prism server, then set up the channel to use its URL instead of its hostname or IP address. For example, in the Console, open File|Console Settings|Server tab and change the entry to, for examaple,  www.YourWebSite.com. The Prism server would have to be in a DMZ zone, not behind your firewall. 

The following technique might work, but it would require two images - one for inside, one for outside. You may want to test it.

-Configure the Prism server to us its internal IP address.

-Generate a subscription file for the inside computers to use the internal IP address of the Prism server instead of its host name.

-Generate a subscription file for the outside computers to use the external IP address of the Prism server instead of its host name. If you set up NAT on your firewall, perhaps outside clients polling the external address will be passed through to the internal IP address of the Prism server.





New Boundary Technologies Support
support@newboundary.com

Post #965
Posted 9/2/2005 12:48:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 9/1/2005 10:03:00 PM
Posts: 1, Visits: 1

We have the same issue.

We are evaluating the Prism suite right now and we have a large number of client systems that will reside outside of the LAN/firewall.  A small number inside the LAN/firewall.  And some systems that will move back and forth between both.

Other products, Centennial's Discovery, for example, allows you to have two entries (one internal, one external) for this exact reason.  The agent tries the first entry and if unable to connect, it uses the second entry.

I don't understand your suggestion.  What does IIS have to do with anything?  Does Prism use IIS in some way?  How are you defining "web address" versus "host name"?  The term "www" is actually a host name (just a standardized one used for most web sites) and doesn't require a web server. 

We definitely need this functionality.  We're going to try to create different deployment using internal and external but it is extra work trying to guess if a machine will always be on the inside or outside of the firewall in the future.  And for laptops, it is impossible to pick one or the other.

Is there any plan to fix?



---------------------------------
Kent Schum

Post #1035
Posted 9/2/2005 1:23:00 PM


Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800

We agree that it would be useful to give the client multiple entries to try when contacting the Prism server. This request is in our tracking system to be evaluated by the product management team for inclusion in a future release.

 

The Prism server can be identified one of three ways: 1) its computer name (on the LAN); 2) its IP address (on the LAN or WAN); 3) its URL (only when Prism is installed on a web server).  Our posting suggests installing Prism on a web server so that internal and external PCs can successfully communicate with it.

 





New Boundary Technologies Support
support@newboundary.com

Post #1036
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: New Boundary Support

PermissionsExpand / Collapse

All times are GMT -6:00, Time now is 10:25am

Powered By InstantForum.NET v4.1.3 © 2008
Execution: 0.375. 12 queries. Compression Enabled.