Shared folder permissions

[vclawson]

I am having issues with shared folder permissions. Here is the scenario:
1. User1 shares folder to internal user
2. User2 accepts the share
3. User2 attempts to open document in shared folder
4. An Authentication window pops up to login.

Now, User2 is already logged in. Why is user2 prompted to login at this time? This only happens with some users and therefore leads me to believe is is a permissions issue for the user. Any assistance would be greatly appreciated.

Thanks

[uxbod]

Are they both connecting to the same URL for ZWC ? Are you in a multi-server setup ? Have you set a Public Hostname with the Admin GUI ?

[vclawson]

yes, some users in the same domain are expeiencing this issue while others do not. This is a single server environment. the public host name on one domain that is experiencing the problem has been set but not on the other. I tried setting this and tested again and get the same results. Would anything need to be reset for this?

[uxbod]

Is the public hostname resolvable by DNS from the other domain ?

[vclawson]

How exactly would I be able to tell that. I can ping the domain from the server and it comes back with the correct ip address and the actual hostname of the server. What else can i do to determine this?

[vclawson]

I have confirmed that our main domain does not have this issue. For example:
User1 in otherdomain.com shares a folder with user2 in maindomain.com
User2 logs in and links to the folder and is able to open the documents.
However, user3 in maindoain.net is prompted to authenticate.

So any user other than the domain of the server is having this happen.

on the other domains should the public service host name be something like mail.otherdomain.com or should it be mail.maindomain.com or the actual hostname of the server?

Thanks

[vclawson]

DNS information
root@mail:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
216.83.153.18 mail.maindomain.com mail

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

root@mail:~# cat /etc/resolv.conf
search maindomain.net
nameserver 4.2.2.2

root@mail:~# dig otherdomain.com mx

; <<>> DiG 9.4.2-P2 <<>> otherdomain.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41698
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;otherdomain.com. IN MX

;; ANSWER SECTION:
otherdomain.com. 2688 IN MX 0 mail.maindomain.com.

;; Query time: 19 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Tue Apr 6 10:53:53 2010
;; MSG SIZE rcvd: 59

root@mail:~# dig zriimail.com any

; <<>> DiG 9.4.2-P2 <<>> otherdomain.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44416
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;otherdomain.com. IN ANY

;; ANSWER SECTION:
otherdomain.com. 2611 IN MX 0 mail.maindomain.com.
otherdomain.com. 2611 IN A x.x.x.x ip address of Zimbra server
otherdomain.com. 1506 IN NS ns13.domaincontrol.com.
otherdomain.com. 1506 IN NS ns14.domaincontrol.com.

;; Query time: 16 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Tue Apr 6 10:55:10 2010
;; MSG SIZE rcvd: 127

root@mail:~# host `hostname`
mail.maindomain.com has address x.x.x.x (matches ip address above)

[vclawson]

Somebody mentioned that there is no MX record in the information I posted above. This line is there:
otherdomain.com. 2688 IN MX 0 mail.maindomain.com

but is this incorrect? Should the MX be pointing at the main domain or have it's own mx record such as mail.otherdmain.com and would this cause the permissions issue?

[uxbod]

It is fine to point the MX at your primary domain; the issue is that mail.maildomain.com is not resolving. You should see the IP address of your Zimbra server when that dig query is performed.

[uxbod]

I gathered the name of your domains from the information above and you have no rDNS entry for your mailserver.