Search results for query: *

If GroupWise is not an option, download and run this file: http://www.novell.com/coolsolutions/tools/downloads/mltoins.exe This will put GroupWise as the default mail handler.

You also need to do a Java -exit before starting the install. If the java files are locked, you'll get all kind of weirdities.

The same thing happens here everytime we move a person. WE tell them in their move announcements that if you are the recipient of shared folders, you will lose them Sorry. I've opened incident with Novelll and got no resolution. Please post if you have any luck with this.

I know that in GW6 the rule replying once is by design. A workaround I have used is to add the line Subject=* to the rule. This way it will repy each time and you won't have to reconfigure your domain. If you do enable the "old style" rule execution, be sure to not allow rule...

Run Poledit, File-open registry, Local User-Control Panel-Display. Make sure "Restrict Display Control Panel" is not checked. Click OK-Save-Exit. I have seen tools mess this up before. Hope this helps. David

Just 1 wild guess.. Is there any chance that your users GroupWise ID starts with the letters "PU"? We had a similar problem and it turns out that GW cannot maintain ANY ID's who's first letters are "PU". These letters are reserved for prime user databases. I don't really...

No, You cannot access GroupWise WebAccess with both 5.5 and 6 directly. There are differences in the MTA's and the MTA's must match WebAccess. You can setup a secondary domain and run WebAccess under this domain. I setup a secondary 5.5 domain and put only webaccess under it. I linked the MTA's...

I have replaced 2 Linksys routers within the last year for the symptom you describe. 1 was fixed under warranty and the other I had to buy. I ASSUME this is a relatively common failure mode for the Linksys.

Documents will not appear in a search until after the next index job. We are set to index once a day, therefore, it is the next day before Users can search their docs. If you need it faster, you'll probably want to consider an indexing server. Running indexing on the same box really slows things...

I have seen similar problems quite a few times. Try nslookup and see if you get a valid IP address. If you can PING it OK, DNS is OK. If PING works and NSLOOKUP does not, the problem is in your IP stack on the box. You may need ro remove and reinstall IP to get this to work. Like I said, I've...

I am trying to install Webaccess and am having one heck of a time with the address book. In my lab setup, I have 2 PO's and 4 Users. I can access all functions fine in WebAccess except the address book. Without exception, the webaccess address book takes 14 minutes to come up. I don't see...