Issues getting JDS to work in the cloud

[yadmin]

Hi All,

Not sure if i'm missing something here, but I'm having issues with getting our JDS up and running in the cloud.

So to paint a picture of our setup:-

We have a our JSS setup in the cloud and a local JDS (on Mac) setup in our London Office. I am now trying to setup a JDS in the cloud for external staff to hit.

I've setup and Ubuntu 12.0.4LTS server and run the JDS installer and gone through and entered in the hostname etc etc. The JDS enrolls and is visible in the JSS. Currently we are using self-signed certs at this point. This is a test lab before we actually make the leap.

I can hit the JSS internally and externally and can enroll machines no problem. However i can't mount the http://cloudhostedjds/CasperShareDAV on my mac. It prompts for creds and will mount with readonly creds but not the readwrite and the password is def correct. So when using Casper Admin it can't mount the cloudhostedJDS, however If i set the MachostedJDS as the root JDS, that mounts fine.

As a result the replication is also not happening between the two JDSs.

It's driving me crazy. I've trusted the self-signed certs on our test machine that I'm testing casper admin on etc so can't see it being a cert issue.

Any changes i make to the account username and password in the JSS I see replicated in the .DAVlogin in /usr/local/jds/shares/.DAVlogin. I've not yet changed the ssh port on the JDS, only on the JSS but can't see that being an issue as the MacJDS works fine.

Am i missing something here? is there some additional configuration need in Ubuntu?

[gskibum]

Did you make any progress? I've been having the same issue.

Edit: I've been having the same issue with OS X Server Mavericks.

[justinrummel]

I was doing a JumpStart this week and were trying to do something like this and it failed. The setup was a Ubuntu 12.04 JDS hosted via Windows Azure. The interesting item is the "internal" IP address was a 100.x.x.x network vs. a non-routable IP address (10.x.x.x, 192.168.x.x, or 172.16-31.x.x). When the JDS / Apache tried to validate it's address it always picked up this IP vs. an internal or the true "public" IP. Once we put the JDS on a more traditional Ubuntu server that was part of a NAT network, it worked as expected.

Hope to fine out more from JAMF Support.

- Justin

[gskibum]

Thanks Justin. Your post congeals some ideas I had sloshing around in my head. I was just now looking at the DNS records & zones, and my private IP addresses.

At the moment I don't think my issue has anything to do with Casper, but is rather a networking-DNS issue. I've broken my test JSS to the point the internal JDS doesn't work anymore. :-)

[justinrummel]

@gskibum Break it big... or don't even try. ;)

BTW; when standing up the internal JDS we did update the /etc/hostname to the jds dns host and /etc/hosts file. So if our jds DNS name was jds1.domain.tld we would have:

/etc/hostname
jds1

/etc/hosts
127.0.0.1 localhost
127.0.1.1 jds1
### bunch of ipv6 crap below ###

Make sure that jds1.domain.tld has the proper dns records (internal and external if split DNS configuration) so Casper Admin can mount the WebDAV share.

- Justin