Announcements
Hi guys,
I installed the GP and web client in our company's domain.
Now my boss told me he want to access GP through web client when he is going to business trip.
Is it possible to access GP from extranet? For example, when he connect to the hotel public wifi.
I don't know much about the nework and just installed the gp according to the official documents.
Thank you very much.
*This post is locked for comments
Good Day, can anyone advise the requirements to have GP Web Client work external to the network?
Is it only a third party ssl certificate that is required? Or are other things needed? The documentation on web client does include details on this. So if anyone else got this to work, it would be appreciated if they can share what was done.
Thank you very much.
Hi Derek, is this the same requirement for today in 2022? If the web client is already set up for local network access, will it need to be reconfigured for it to be accessed externally?
Hi Kerry, can you elaborate more on how your setup works? My understanding is that we need to first add a DNS record to point gpwebaccess.mydomain.com to one of our external IP addresses. Next, we need to do some NAT (network address translation) on our firewall for example to forward traffic from gpwebaccess.mydomain.com to the internal server/IP running the IIS Web Server. For this to happen, some ports on the firewall will need to be open so that outsiders can access the web Server. If using Azure AD, no need for the web server to access internal domain controller but still the web server will need to access SQL Server. Let me know your thoughts on this or if there is another post that discusses this setup somewhere.
Hi All,
Did anyone publish GP over the internet successfully?
i am also getting some sort of same issue while accessing GP Web Client out side the network or over the internet. after taken the user ID or password, only the screen i can see is " wait we are getting things ready".
my current situation is when i installed/configure GP Web Client, i define the fully host name like servername.domain.com (FQDN) which is default, but are live web address is like https://www.domain.com/GP. we buy third party certificate later and import in the server. at the time of installation/configuration i used Self-signed certificate.
please let me know the possible cause and its solutions.
Regards,
Muhammad Moin.
This is a very broad question but yes you can. You have many options just depends on your network setup and level of risk your company is comfortable with. We do this all the time with our employees. We chose to do this using organizational accounts (Azure AD) for web client authentication. This method allows you to configure 2-factor and creates a secure tunnel between internal network and internet. You literally only need to open outbound ports, no inbound required. Ideally you would place the web server in the DMZ not joined to the domain but MS does not allow this, unfortunately it must be domain joined. Also you can lock down communications between the web server and SQL server via firewall.
Any update on this ?
Can we access GP outside our domain, purchasing 3rd party SSL Certificate ?
Regards.
Hello Howard,
By default, if you're using Web Client setup with a self-signed certificate created through IIS Manager or the Certificate Authority, only users that are on the same domain as where Web Client is installed, would be able to access Web Client. The certificate would need to be imported and exported onto each machine that is accessing Web Client within the domain.
In order to make Web Client accessible externally, we would recommend using a third-party certificate, such that you can get from GoDaddy.com or another vendor such as this, which will setup the certificate so instead of using the default machinename.domain.com/GP URL to access Web Client, you'll be able to use something like https://MyCompany.com/ which, using DNS settings, will allow users to use that URL externally from the domain/network, without exposing your domain name to the Internet.
Thank you,
hi howard,
i assume that you use for security reasons an internal ip-address (10..., 192...) for the webclient. to get connected to the webclient from the web, this is in first place a network and firewall configuration. you need an ip-address and/or a host/domainname that is accessible from the web, which is routed to the internal used ip-address. you can also set an alternate port for external usage, e.g. external ip 214.x.y.z:80 points to internal ip 10.0.0.1:8080. the external port needs a rule in the firewall settings. contact your sysadmin for help.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
