Johnnie Odom's questions

Have a bit of a GW problem, and I'm a bit stumped using the usual sources ( forums, TIDs, etc. ) even though the issue is theoretically quite straightforward.

The primary problem: I cannot set up a new PO on an OES2 sp 2 server that is already running an MTA. The secondary problem: The reason I cannot set up the PO appears to be an issue with setting up an SDD that the Linux server can access.

Platforms: OES 2 sp2 with GroupWise 8.0.2 (without the hot patch released a couple of days ago). All but one of my existing POs is hosted on Netware. The non-Netware PO is also on OES2 sp2 but I set it up about two years ago and my memory of the process has faded ....

My problem appears to be identical to this forum posting: http://forums.novell.com/novell-product-support-forums/groupwise/groupwise-8x/gw8-agents/423407-can-not-create-po.html

In Detail: I am trying to set the PO up at path /media/nss/MAIL/gwpost The gwpost directory is writable by both root and the eDirectory user I am using with ConsoleOne. I have attempted to use ConsoleOne (as installed from GW 8.0.2 media) from both the OES server itself and Windows 7 to create the PO. Everything goes well until I get to the last stage of the PO creation screens -- after clicking "Finish" the GroupWise installer tells me that it cannot access the SDD and gives me a warning. Even if I ignore the warning, it dumps me back to the first PO creation screen. I do not have a standard SDD for Linux GroupWise so I am creating a new one for this particular project.

So, all indications are that I have a bad SDD, but given the forum post I am not ruling out a GroupWise bug (that said, the recent hot patch does not seem to have any fixes listed that would solve this issue). I do know that Linux SDDs can be tricky.

Novell TID 7005157 goes into some of these issues: http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005157&sliceId=1&docTypeID=DT_TID_1_1&dialogID=182591620&stateId=0%200%20182593086

I have tried the following: 1. Using the GroupWise installer and ConsoleOne to create an SDD at /media/nss/MAIL/software and attempted to access it via NCP share. 2. Using the GroupWise installer and ConsoleOne to create an SDD at /media/nss/MAIL/software and attempting to access it via the Linux path (with and without values in the UNC path per the TID) 3. Using the GroupWise installer and ConsoleOne to create an SDD at /opt/novell/groupwise/software and attempting to access it via the Linux path (without values in the UNC path per the TID)

All of these SDDs have resulted in the same error, per my description and the forum post above. I have checked the rights for both root and the eDirectory user for all of the SDDs above.

I've been working on this for two days and am stumped. Any ideas? Has anyone seen this?

This seems like one of those questions that has a simple answer I am not seeing.

We have an IIS server hosting multiple websites, each site on a separate IP. Some of these sites are running ASP and ASP.NET applications. I have one site whose primary purpose in life is to serve updates for Sophos antivirus, which are basically static file sets. The OS X package for Sophos contains a file that ends with a .config extension. IIS refuses to serve this file (which is key to the update process) because it believes that it is part of an application. The error IIS returns is 403.1.

What I want to do is configure this single IIS site / virtual directory such that files ending with .config are served as regular text or similar so that the Sophos client can update properly. Preferably this would be set so that other sites on the same server would not be affected (i.e. no turning the ASP.NET extensions off). So far, specifying that .config is text/text and application/octet-stream in MIME has not helped (MIME is otherwise set to ".* All"). Neither has setting permissions for the site's virtual directory to read-only and removing script running permissions (that simply changes the error from 403.1 to "Service Unavailable").

Other than just admitting defeat and setting up Apache on a Linux box somewhere, what should I be doing here? Thanks in advance.