Anonymous_User Absent Member.
Absent Member.
2379 views

Accessing iFolder from Internet Fails

We are having difficulties accessing iFolder fromt the
internet/extranet.
A Link on our hosted web site only works when accessed internally. We

implemented TID regarding placing the Public IP address in the link on

Ifolder_nav.html. Once completed the link does launch the iFolder
page
however login fails with Cannot find server.

Our DNS record for the iFolder service is ifolder.xxxx.com
BM reverse proxy has been setup with standard access rules with
authentication enabled for access.

Do we need our ISP to resolve iFolder.xxxx.com to a specific Public IP

address i.e our Web Server or perhaps a different Public IP. or is
this
not necessary.

Our BM Server OS is 5.1 with all other servers 6.0 is this perhaps a
SSL
compatibility issue.

Would a LDAP issue on the BM server cause access issues?

It just seems when accessing any HTTPS services externally nothing
works...

Do we need specific NAT Entries on the BM?

Your input is greatly appreciated

Best Regards,

William




Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Accessing iFolder from Internet Fails

It sounds like you are having the same problem I did in figuring out
how to
forward proxy iFolder.

1. First off, you should have a DNS name point to a public IP address
that
you want to use for iFolder.
2. Second, you want to add that secondary IP address to your BM box.
3. In your acceleration page, go to the details of the http
acceleration and
add a forward proxy both for port 80 and port 443 for your ifolder.
4. Next, you need to add some openings in your firewall filters. I
still
use filtcfg. Add an opening from the public interface to the privateinterface (you can specify the host of the ifolder server if you want)
for
port 80 and port 443. There may be other ports that you need to open
for
response back, but I already had those open. Check the TIDS for
adding
filters for webserver behind firewall.

Hope this helps.
Dan.


<william@hitecsolutions.com> wrote in message
news:mQc0a.11380$EM3.10780@prv-forum2.provo.novell.com...
> We are having difficulties accessing iFolder fromt the

internet/extranet.
> A Link on our hosted web site only works when accessed internally.

We
> implemented TID regarding placing the Public IP address in the link

on
> Ifolder_nav.html. Once completed the link does launch the iFolder

page
> however login fails with Cannot find server.
>
> Our DNS record for the iFolder service is ifolder.xxxx.com
> BM reverse proxy has been setup with standard access rules with
> authentication enabled for access.
>
> Do we need our ISP to resolve iFolder.xxxx.com to a specific Public

IP
> address i.e our Web Server or perhaps a different Public IP. or is

this
> not necessary.
>
> Our BM Server OS is 5.1 with all other servers 6.0 is this perhaps a

SSL
> compatibility issue.
>
> Would a LDAP issue on the BM server cause access issues?
>
> It just seems when accessing any HTTPS services externally nothing

works...
>
> Do we need specific NAT Entries on the BM?
>
> Your input is greatly appreciated
>
> Best Regards,
>
> William
>






0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Accessing iFolder from Internet Fails

Thanks much Dan for the insight,

In understanding your configuration, here are a few questions.
1. The DNS name ifolder.myfirm.com was setup internally on our DNS
Server
and resolves to the private secondary IP address located on the web
server
(not BM). We have also had our ISP configure an 'A' record to one of
our
Public IP's. Is this necessary or can we use our 'www' record (single

Public IP). and are you referencing us to add a public IP address
within
our DNS?
2. When adding the secondary IP address to the BM are we adding this
IP
under IP Addresses listed for marking Public or Private?
3. We follow you on this, no problem
4. Yes we too use 'filtcfg'and work many hours getting filters to
work.

Thanks for your help,

William


> It sounds like you are having the same problem I did in figuring out

how
to
> forward proxy iFolder.
>
> 1. First off, you should have a DNS name point to a public IP

address
that
> you want to use for iFolder.
> 2. Second, you want to add that secondary IP address to your BM box.


> 3. In your acceleration page, go to the details of the http

acceleration
and
> add a forward proxy both for port 80 and port 443 for your ifolder.> 4. Next, you need to add some openings in your firewall filters. I

still
> use filtcfg. Add an opening from the public interface to the

private
> interface (you can specify the host of the ifolder server if you

want)
for
> port 80 and port 443. There may be other ports that you need to

open for
> response back, but I already had those open. Check the TIDS for

adding
> filters for webserver behind firewall.
>
> Hope this helps.
> Dan.
>
>
> <william@hitecsolutions.com> wrote in message
> news:mQc0a.11380$EM3.10780@prv-forum2.provo.novell.com...
> > We are having difficulties accessing iFolder fromt the

internet/extranet.
> > A Link on our hosted web site only works when accessed internally.

We
> > implemented TID regarding placing the Public IP address in the

link on
> > Ifolder_nav.html. Once completed the link does launch the iFolder

page
> > however login fails with Cannot find server.
> >
> > Our DNS record for the iFolder service is ifolder.xxxx.com
> > BM reverse proxy has been setup with standard access rules with
> > authentication enabled for access.
> >
> > Do we need our ISP to resolve iFolder.xxxx.com to a specific

Public IP
> > address i.e our Web Server or perhaps a different Public IP. or is

this
> > not necessary.
> >
> > Our BM Server OS is 5.1 with all other servers 6.0 is this perhaps

a
SSL
> > compatibility issue.
> >
> > Would a LDAP issue on the BM server cause access issues?
> >
> > It just seems when accessing any HTTPS services externally nothing


> works...
> >
> > Do we need specific NAT Entries on the BM?
> >
> > Your input is greatly appreciated
> >
> > Best Regards,
> >
> > William
> >

>
>





0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Accessing iFolder from Internet Fails

It's all about the access addresss. A given user must access iFolder
via
the same DNS name whether they are internal, external, proxied or
direct.

Do you want internal users to access directly and public users to
access
via BM reverse proxy? If so, you need private user to resovle the DNS

name to resolve to the private address of the iFolder server. You
will
want public users to resolve this same DNS name to the public address
of
the reverse proxy.

> Thanks much Dan for the insight,
>
> In understanding your configuration, here are a few questions.
> 1. The DNS name ifolder.myfirm.com was setup internally on our DNS Server
> and resolves to the private secondary IP address located on the web


server
> (not BM). We have also had our ISP configure an 'A' record to one

of
our
> Public IP's. Is this necessary or can we use our 'www' record

(single
> Public IP). and are you referencing us to add a public IP address

within
> our DNS?
> 2. When adding the secondary IP address to the BM are we adding this

IP
> under IP Addresses listed for marking Public or Private?
> 3. We follow you on this, no problem
> 4. Yes we too use 'filtcfg'and work many hours getting filters to

work.
>
> Thanks for your help,
>
> William
>
>
> > It sounds like you are having the same problem I did in figuring

out
how
> to
> > forward proxy iFolder.
> >
> > 1. First off, you should have a DNS name point to a public IP

address
> that
> > you want to use for iFolder.
> > 2. Second, you want to add that secondary IP address to your BM

box.
> > 3. In your acceleration page, go to the details of the http

acceleration
> and
> > add a forward proxy both for port 80 and port 443 for your

ifolder.
> > 4. Next, you need to add some openings in your firewall filters.

I
still
> > use filtcfg. Add an opening from the public interface to the

private
> > interface (you can specify the host of the ifolder server if you

want)
> for
> > port 80 and port 443. There may be other ports that you need to

open
for
> > response back, but I already had those open. Check the TIDS for

adding
> > filters for webserver behind firewall.
> >
> > Hope this helps.
> > Dan.
> >
> >
> > <william@hitecsolutions.com> wrote in message
> > news:mQc0a.11380$EM3.10780@prv-forum2.provo.novell.com...
> > > We are having difficulties accessing iFolder fromt the

> internet/extranet.
> > > A Link on our hosted web site only works when accessed

internally.
We
> > > implemented TID regarding placing the Public IP address in the

link
on
> > > Ifolder_nav.html. Once completed the link does launch the

iFolder
page
> > > however login fails with Cannot find server.
> > >
> > > Our DNS record for the iFolder service is ifolder.xxxx.com
> > > BM reverse proxy has been setup with standard access rules with> > > authentication enabled for access.
> > >
> > > Do we need our ISP to resolve iFolder.xxxx.com to a specific

Public
IP
> > > address i.e our Web Server or perhaps a different Public IP. or

is
this
> > > not necessary.
> > >
> > > Our BM Server OS is 5.1 with all other servers 6.0 is this

perhaps a
> SSL
> > > compatibility issue.
> > >
> > > Would a LDAP issue on the BM server cause access issues?
> > >
> > > It just seems when accessing any HTTPS services externally

nothing
> > works...
> > >
> > > Do we need specific NAT Entries on the BM?
> > >
> > > Your input is greatly appreciated
> > >
> > > Best Regards,
> > >
> > > William
> > >

> >
> >

>





0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.