Novell client install problem
Nanu Kalmanovitz
I'm trying to follow the Novell Client for Linux on a SLED 10 sp2 computer.
Following the instructions at http://www.novell.com/documentation/linux_client/ncl20_installqs/index.html?page=/documentation/linux_client/ncl20_installqs/data/b5qt8ou.html:
1. Launch the YaST Control Center.
2. GNOME: Click Computer > More Applications > System > YaST.
3. If you are not logged in as root, type the root password, then click Continue.
4. Click Software in the left column, then click Add-on Product in the right column.
5. Select the appropriate Add-on Product source (such as CD, DVD, or Local Directory), then click Next.
6. Select Yes, I Agree to the License Agreement, then click Next.
7. Select Patterns from the Filter drop-down list.
8. Select Novell Client for Linux in the Additional Software category.
The problem is that the " Novell Client for Linux" doesn't appear in the Additional Software category.
Other software are checked there: Novell Applications, Help and Support Documentation, Novell AppArmor.
How can I solve ot?
TIA
Nanu
Joseph Marton
> The problem is that the " Novell Client for Linux" doesn't appear in
> the Additional Software category.
Novell Client isn't included with SLED. You'll need to download it.
http://download.novell.com/Download?buildid=bldJIQnntfA~
Once you download the ISO you should be able to point the add-on product
screen to the ISO using the "local directory" option.
--
Joe Marton
Novell Support Forum SysOp
See what GroupWise 8 can do for you.
http://www.novell.com/products/groupwise/
Nanu Kalmanovitz
It looks it was installed successfully, but now I expect to see the known login window novell as it appears on M$ win stations.
Login form the Suse login field, the network icon on the lower bar display a "Not connected" status. Clicking the icon and choosing "WIRED CONNECTION", it connect to the network and the status become "Wired".
The system also display the error message: "The novfs loadable module is not installed correctly".
Please help
TIA
Nanu
>>> Joseph Marton<jmar...@SPAMhsemuni.com> 21/11/2008 15:49:21 >>>
Joseph Marton
> It looks it was installed successfully, but now I expect to see the
> known login window novell as it appears on M$ win stations.
The Novell Client for Linux acts different from Windows. Windows has the
GINA and as such the Novell Client can integrate with it. In fact, even
this is only true up to and including XP. Even Vista is different since
it no longer has a GINA, so in those regards what you see with NCL & SLED
isn't all that different from what Vista users see.
At any rate, the idea is that the NCL login is a completely separate
process. After you login you can right-click on the 'N' icon in the
bottom righthand corner (the Novell Tray icon) and login from there. You
can also do it by going to Computer->More Applications and running the
Novell Login program. Either way, the screen that comes up looks just
like the Novell login screen you're used to seeing on Windows.
Another option is "integrated login." What happens is that you login
once using the Novell login program and have it save your profile. Then
for now on when you log into SLED, NCL automatically logs you into eDir
using your previously saved credentials.
If you don't want to use integrated login but don't want to have click on
several icons just to get to the login screen, the last option is to make
the Novell Login program a startup application. In other words, each
time you log into SLED the program will run which means you'll get the
Novell login screen automatically every time you log into SLED. Of
course this means having to log in twice, once to SLED, and once to eDir.
> The system also display the error message: "The novfs loadable module is
> not installed correctly".
Hmm... you're NCL installation isn't working properly, then. I remember
from the other thread that you had updated to SLED 10 SP2. Did you apply
any post-SP2 updates? I think this issue is resolved if you have the
latest kernel. Please post the output of this command.
uname -a
Until this is fixed, I don't believe the Novell tray icon is going to
appear. Even if it did, it wouldn't work.
Nanu Kalmanovitz
Linux linux-PIII 2.6.16.60-0.21-default #1 Tue May 6 12:41:02 UTC 2008 i686 i686 i386 GNU/Linux
Joseph Marton
> Linux linux-PIII 2.6.16.60-0.21-default #1 Tue May 6 12:41:02 UTC 2008
> i686 i686 i386 GNU/Linux
That's the original SP2 kernel. Please update your system with the
latest patches, which will get you the latest kernel. Also, make sure
you have the following packages installed.
kernel-source
gcc
gcc-c++
Nanu Kalmanovitz
Can u give me a URL?
Are there any installation instructions?
TIA
Nanu
>>> Joseph Marton<jmar...@SPAMhsemuni.com> 21/11/2008 21:35:42 >>>
Joseph Marton
> I tried to find the patches and install them using the automatic update
> but they didn't find any.
Did you register your installation of SLED?
Nanu Kalmanovitz
I found the TID 3132246 which help me with the SLED registration. I hope it solved the automatic update problem.
What the "uname -a"should display?
How to check that the following pacjages are installed:
kernel-source
gcc
gcc-c++
TIA
Nanu
>>> Joseph Marton<jmar...@SPAMhsemuni.com> 24/11/2008 15:57:41 >>>
Joseph Marton
> What the "uname -a"should display?
2.6.16.60-0.31 I believe. Definitely newer than .21.
> How to check that the following pacjages are installed:
>
> kernel-source
> gcc
> gcc-c++
YaST->Software->Software Management
Do a search for those packages.
Nanu Kalmanovitz
>> 2.6.16.60-0.31 I believe. Definitely newer than .21.
Where can i find a "key" that explain what those digits represent?
TIA
Nanu
>>> Joseph Marton<jmar...@SPAMhsemuni.com> 24/11/2008 18:07:37 >>>
Joseph Marton
> Where can i find a "key" that explain what those digits represent?
There really isn't. I just happen to have some of the kernel versions
memorized. :-)
Nanu Kalmanovitz
The new problem is that the netware scripts can't map to the volumes on the diferent netware servers.
The error message is "Unable to map F:=........ (code:8804).
I didn't find any TID. Please help.
TIA
Nanu
>>> Joseph Marton<jmar...@SPAMhsemuni.com> 21/11/2008 21:35:42 >>>
Joseph Marton
> The new problem is that the netware scripts can't map to the volumes on
> the diferent netware servers. The error message is "Unable to map
> F:=........ (code:8804).
I'll give you a tip, but if this doesn't work, please start a new
thread. First, you need to make sure that SLP is configured on your
network and that at least one of your servers is an SLP DA. Then you
have to configure the system settings for the Novell Client by right-
clicking on the N system tray icon and choosing system settings (I
believe). Make sure you then configure the SLP settings in the client
and point it to your DA (or DA's).