yes, everything is working today. and so is owncloud from the outside.

Cname did the trick. Thanks everyone.

so whoever hosts the DNS for my domain should be able to create a CNAME to alias owncloud.roseradiology.com to owncloud.rose.internal? Correct?

@Dashrender so a split horizon DNS would be creating a zone for roseradiology.com and then adding internal records for mail, www, etc

Our new active directory domain is rose.internal so would that be the top level domain?

so what is the best practice here? set everything twice?

so is it better to keep it on rose.internal and register that domain?

@JaredBusch So its a bad idea right?

So if I add a record for mail.roseradiology.com that should fix?

yes and it does not

Our new domain name is rose.internal and we have joined all workstations, servers, and DC's to rose.internal. I have an external DNS record pointing owncloud.roseradiology.com to a public address. I dont want to change that unless I have to. Being that our new domain is rose.internal and owncloud's address is owncloud.roseradiology.com I added a new zone to DNS called owncloud.roseradiology.com and pointed it to internal IP. Works OK. But several centers cant reach webmail at mail.roseradiology.com Where do I start to fix this? Im sure Im going to catch hell from several ML members.

Hoping to sell. Open house today.

@Dashrender TO the computer

Thanks Jared. Had to enable inbound remote administration exception in group policy. I appreciate your help.

Since joining the new domain i can no longer \IPADDRESS into anything. What has to be done in group policy to allow this?

@travisdh1 i did one in VBOX and had the same issue, curious...

i disabled prepopulate printer search in local group policy to see if that fixes it

@Dashrender they are being added, installed

workgroup joined, upgraded from 8.1 to 10, ill check GPEDIT.MSC

Does anyone know what setting controls this so I can turn it off?

Thanks Scott! Works Perfectly!