Skip to main content
Question

AWS Commserve Hostname

  • May 19, 2026
  • 9 replies
  • 48 views

Forum|alt.badge.img+1

We have a commserve in AWS, which host name is its ip address. We can access the web portal with the ip as a url on Windows laptops, however other members who use a mac machine cant. From what I gather from minor research if I create a proxy server with a fqdn this should resolve the issue for the MAC users and the ip cache issue.

Has anyone ever dealt with something like this? Or have an alternate solution, that does not involve changing the hostname of the commserve itself?

9 replies

Forum|alt.badge.img+17
  • Vaulter
  • May 20, 2026

HI ​@Amy Jo ,

Kindly review the below configuration and share the results.

  • Ensure Mac machines are on the same network as the Windows laptops.
  • Try to ping the web server IP from a Mac to confirm basic connectivity.
  • Confirm that the firewall on the web server allows inbound connections on the required ports (typically 80 for HTTP or 443 for HTTPS) from all client subnets, not just Windows devices.
  • Try adding the IP and hostname mapping to the Mac’s /etc/hosts file.

Scott Moseman
Vaulter
Forum|alt.badge.img+23

Mac laptops cannot access the CS by IP address?  Can they ping the IP address?

Thanks,
Scott
 


Hello,

I’ve tried adding the IP address and hostname mappings to /etc/hosts/, however I still was not able to ping the server. To add a bit more context, we need some way of configuring a hostname to the IP address that host the AWS commserve resides on so that we can access it on a our internal network.  The only issue is that we don’t have an actual hostname tied to the IP address of the commserve that we can configure with our internal network. Do you all have any recommendations around this issue? The easiest solution we’ve come across is setting up a proxy server, but wanted to know if there’s anything else you’d recommend.

 

Best,

Chibueze


Scott Moseman
Vaulter
Forum|alt.badge.img+23

I’m not sure I’m following.  Do the Macs have a connectivity or DNS resolution issue?

Fixing the DNS resolution will not help if the Macs are unable to access the CS by IP.

Thanks,
Scott
 


Macs are able to connect to the commserve by IP, however we want to add the commserve to be accessible in our internal network (without VPN), but it’s needs to have an actual hostname in order to be configured.

 

Best,

Chibueze


Scott Moseman
Vaulter
Forum|alt.badge.img+23

OK, so there’s not a connectivity issue. You mention Windows clients can access via URL, but the Mac clients cannot? Are they using different DNS servers? I think there’s some context to this issue which I’m not understanding.

Thanks,
Scott
 


No, to my knowledge MACs are not using different DNS servers. We’ve configured CNAME records to the IP address through our internal network, but the commserve is only accessible by those aliases without issue on Windows Machines and not MAC.

 

Best,

Chibueze


Scott Moseman
Vaulter
Forum|alt.badge.img+23

Can the Macs ping the alias?  If they can access the CS by IP (connectivity) and can resolve the alias (DNS) then I don’t really know what to suggest.

Thanks,
Scott
 


I can ping the alias from my MAC, yes.

 

Best,

Chibueze