Solved

Using Groupwise 4.1a on a NT worksation SR 3

Posted on 1998-09-29
3
185 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 100 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

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

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

Here's how to start interacting with our community through Post.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…

728 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