?
Solved

Using Groupwise 4.1a on a NT worksation SR 3

Posted on 1998-09-29
3
Medium Priority
?
186 Views
Last Modified: 2006-11-17
I am trying to use Groupwise 4.1a with post office on a Netware 4.11 server.  I can not get the NT Workstation to successfully logon to with the Groupwise Client.  Is there a set protocol for accessing Groupwise from an NT workstation?  If so, What are the steps...?  We are using the Groupwise flawlessly on 3.11 and 95 machines...
0
Comment
Question by:Techro
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 

Author Comment

by:Techro
ID: 1593587
Edited text of question
0
 
LVL 3

Accepted Solution

by:
brosenb0 earned 300 total points
ID: 1593588
Prior to upgrading to GroupWise 5.2 (and soon 5.5), we ran 4.1 without a problem on NT desktops.

Here are some tips: -

GroupWise 4.1 checks with NetWare to determine your user name.  In the NDS world and if using a Novell client, this will be fully distinguished ie. USER.OU.ORG.  If using a Microsoft client for NetWare (the one that comes with NT) this will be relative distinguished ie. USER.

If you are using the Novell Client for NT, you have to make sure the user name that GroupWise uses matches the network id configured for the user in GroupWise admin.  There are two ways to get this to match up: -

1) Go into GroupWise admin (AD.EXE) and update the network id field for each affected user so that the network ID field is set to the fully distinguished name.

2) When you run Notify (NTWIN.EXE) or GroupWise (OFWIN.EXE) run them with the command line switch /@u-<groupwise user id>

All startup switches are detailed in the client online help.

Make sure you have the latest client updates or GroupWise may not run under NT.  The current version is release 5, available from support.novell.com/misc/patlst.htm.
0
 

Author Comment

by:Techro
ID: 1593589
The problem was sovled,  simple mistake of not setting the user within the autoexec.bat file with
SET wpcwin=/la-*user*.*container*
0

Featured Post

Introducing Priority Question

Increase expert visibility of your issues by participating in Priority Question, our latest feature for Premium and Team Account holders. Adjust the priority of your question to get emergent issues in front of subject-matter experts for help when you need it most.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is a fine trick which I've found useful many times, when you just don't want to accidentally run a batch script or the commands needs administrator rights.
In the absence of a fully-fledged GPO Management product like AGPM, the script in this article will provide you with a simple way to watch the domain (or a select OU) for GPOs changes and automatically take backups when policies are added, removed o…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question