tjackson

[tjackson]

Thanks for your help. One of my post offices is in a separate tree. Once I logged in to that one as well, it allowed me to define the system and all is working well. It seems that A2GO needs access to all of the servers in the system at the time of system definition, not just the primary domain.

[tjackson]

Although similar, I don’t think our problem is the same. Come to find out, defining the system in XP just took awhile for the new window to open. Once opened, it received the same error after defining the path to the domain as I did on Windows 7.

To rule out any Novell client interference, I have A2Go installed on Windows XP SP2 with only GW Client v8, .net 2.0. It has a mapped drive to the Primary Domain (SLES11 no OES) shared via Samba. The logged in user has full rights to the domain directory.

I no longer get the error message described earlier, however now when I browse to the domain folder it says “This is not a primary domain path”.

Has A2GO been tested against a Samba share on Linux?

[Author]

Replies