This may not be a viable option but I wanted to hear the ideas of the GeoNet first. I have ArcGIS Server (Standard Workgroup 10.4) installed and licensed on a local computer on my company's local area network. I can get to the server manager on this computer by going to :6443/arcgis/manager/site.html .
How can I access this server manager from another computer on the same network? I know the PC's local IP address and have tried all sorts of combinations of accessing this from another PC but have had no luck. I can also see the PC's files by typing in \\and the IP address, etc.. Is this sort of thing possible?
I can see the entire C drive on that machine if I look in a Windows Explorer folder by typing in \\192.168.0.126 . Everything is "shared" on that PC but I am not sure how to get in it from another PC on the same network.
EDIT: btw, that works for me for both the manager and the admin, if I use the machine name (maybe the IP but not the IP), but not if I use the web URL since I have that disabled for the web adapter. Also I should note that I am admin on all my machines with my domain account, so that part isn't is eliminated on my mahcines. just fyi.
I appreciate the extra info. I am excited to try this /admin/login route but unfortunately I just realized that I will not have a VPN connection or a LAN connection until next week sometime. (though, it does work if I remote into the PC and try it!) But, to be clear, are you saying you use the computer's name as opposed to the computer's IP address in place of ""?
Yes, the machine/computer name and the port for both the admin and manager. At least on our network, I would get an error when using the ip....my guess is it is due to the SSL certificate. As for my mentioning the web adaptor not working, that is by design, (recommended for security) that is, I have that disabled on purpose, so to manage, I have to be within our domain (although VPN remote works, since that gets me into the domain).
also, for kicks, try it with http and :6080 My guess is it knows you should be https, and would definitly be need isf you have security enabled, but it's been a while since I did the install (but hope to test 10.4.1 very soon). and if you do have security in place, do you have a SSL installed? Self signed? Seems like I had to have all that, but again, been awhile and our production is still 10.2.2.
My main issue is that I want to publish my data to this 'server' from a different computer than what the server is on. Though, I'm not sure how to make that initial connection to the 'server' computer (which is why I am trying to log into server Manager just to see how to make this connection).
Have you tried that yet? That is the connection you need to publish from another machine. But make ysure you have those rights to publish with whatever account you use in the connection file. If your personal account doesn't have the rights, you can connect as the AGS administrator.
If you have to change your password often, I would recommend NOT storing your user/pass, because if it's like our system, if there are 3 bad attempts, we get locked out and network services staff need to do an unlock. For some reason, these seem to cause an issue, even if you aren't accessing it.
Just fyi, I used ArcMap 10.3.1 on my local machine to publish to an ArcGIS Server 10.2.2 on a server (although that shouldn't matter) just now with this process, and it when smooth, although I had to register the data, which is easily done the the analyze window when publishing. I did this to my dev machine, which has expired ssl certs, and it gave me warnings, (3 I think) but did it just the same. I'm now able to see it in REST directory.
I am trying to install ArcGIS Enterprise along with ArcGIS Pro, so I have created a license file(.json) from MyESRI and have configured it with ArcGIS Portal. I can see ArcGIS Pro licenses in there. I have also installed the License Manager and have authorized it with the same license file. I can see Licenses in the Availability tab there as well. I have cross checked the License Manager hostname in the portaladmin and it is correct along with port number as 27000. Both Portal and License manager are on same machine. Now when I am trying to access and authenticate ArcGIS Pro (which is on diff machine) from Portal. It gives me the following error:
You're almost there. The license manager uses two ports for two separate vendor daemons. Port 27000 is the default port for the lmgrd.exe daemon. you must define another open port for the ArcGIS.exe vendor daemon. After doing so, both ports must be open through the firewall(s). Refer to the following documentation for additional information: -manager/latest/configure-the-arcgis-license-manager-to-work-th...
It could be a firewall issue. I understand that ArcGIS Pro initially communicates with the Enterprise Portal using HTTPS (Port 443) which is typically open. However, it then communicates with the license manager using 27000. If your portal machine has a software firewall, then this will need to be opened. If your License Manager is in a different network security zone to the ArcGIS Pro, then you will need to open 27000 on the perimeter firewall as well.
Hi @Scott_Tansley Thanks for the answer, both the machines are in same cluster and I tried telnet for the portal machine for 27000 port from the ArcGIS Pro machine, and it establishes the connection. I am not sure why I am getting this issue.
Okay, so I only have one client that used Pro with Portal licensing. In New Zealand most people use AGOL because of Civil Defence reasons. It was found that port 27000 wasn't actually being used and it was a totally different port. The client had to work with Esri support to find out which port was being used and then had a new JSON file provided with the specific port number.
Thank you everyone for the help, that was the exact issue. I had to define another for ArcGIS Vendor and then define open it through the firewall through Inbound rules. ArGIS Pro opens up like a charm..Phew....:)
Installing the web adaptor will allow you to disable admin access. Or conversely you could configure ARR on IIS to make it work as a reverse proxy and set your directives to not point to the manager context, but if you're going that route anyway it's considerably easier to just install the web adaptor.
I followed your instructions. The port 6080 was hidden. The rest service directory is created ("stateparkmap.okstate.edu/ousgeog/rest/") with the active windows authentication. However, the public still can access the default rest directory (stateparkmap.okstate.edu:6080/arcgis/rest) without any username and password inputs. In addition, I have created the inbound rule to allow the port 6080/6443 in the server firewall. Could you tell me how I only allow the directory work ("stateparkmap.okstate.edu/ousgeog/rest/")?
In your case, it appears that the GIS Server is installed on the web server with your IIS instance. Is that correct? If so, you can use the Windows firewall to firewall off ports 6080 and 6443 from external traffic (or only allow traffic from the web adaptor to come through those ports)
Since you're using Windows Auth, you should strongly consider configuring your web adaptor to communicate with your GIS Server on port 6443, obtain a certificate from a Certificate Authority, and enable HTTPS/SSL at the web tier.
e59dfda104