Novell Client sees no trees

Have slp running on the server. Using slptool findsrvs service:ndap.novell show the tree. Using slptool findsrvs service: list the da by ip address. However, my windows clients do not see any tree.
I have the service location in my client pointing to the ip address of the da. Also, if I manually put in the ip address for tree, it will show contexts but a search does not show any trees. I have the firewall on my client disabled and the firewall of the server disabled.
Help anyone. Don't know where to go next.

Lee,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

Novell Client 2.0 SP1(IR6) - TID 7008266 - Service/eDir Auth

Shaun et. al.,
I like what I'm seeing in the Novell Client 2.0 SP1 (IR6) release notes.
Tree or Server Not Found on login immediately after powerup is supposedly fixed with this release (a big problem with us).
Can you confirm that TID 7008266 is part of Novell's solution to the issues posed by installing as a Dynamic Administrator / System Account?
(mapping drives, etc).
pitcherj

Well, I think the efforts are completely disconnected.
The Client2 Efforts are nothing to do with ZCM.
I'm aware of the Interactive Services Detection defect and this would
not relate to that in any way. Nor would the Dynamic Administrator
inherit any rights defined by the Client2 Feature.
In regards to the SYSTEM process, it may but I have not tested nor do I
believe anyone in the ZENworks group has done so. However, I think it
would stand a decent chance of working. Of course it would require the
use of a UNC Path, and not drive letters.
On 4/7/2011 12:36 PM, pitcherj wrote:
>
> Craig,
>
> I realize it's not DIRECTLY related to Dynamic Administrator, but I do
> have a SR in with Novell on this (the interactive services detection
> dialog, etc) and they said they were working on an alternate solution
> that would potentially allow users to see the UI of an installer.
>
> (Currently I have to make sure to start the ui0detect service since
> most of the time that service is not active on our user's workstations,
> so they have no way to view the progress of an installer other that the
> ZENwork progress bar)
>
> pitcherj
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

DHCP Conflict between ZfD 4 Agent and Novell Client

I am having problems with the use of Novell Client versions that support
DHCP settings tab (Tree, Context, Server).
This is in this board because my problem is only reproduced when ZENworks
for Destkops 4 (IR5 and IR7) Workstation Management component is installed.
THe problem is this:
Every now and then, logging in with the novell client displays 886f errors
in the login results window, and other strange communication errors.
If I release and renew the IP, it works fine after that.
If I reboot, there is a chance I get the same problem.
This absolutely does not happen when I have the two options for DHCP
settings in the Novell Client unchecked (Server->Binary Data).
Now, is ZfD Workstation Manager getting the Preferred Server IP from DHCP
as well during system startup? Is this clear? Happens on both Windows
2000 and Windows XP.
I have no access to the router serving DHCP so I don't know the details on
that end.

There was (is?) a conflict that is supposed to be solved,
but I'm not 100% convinced that is true. Since I always
use Client32 I remove novdhcp.dll in my ZfDAgent transform,
even now with ZDM7 because I've seen the "semaphore" error
there too if I don't.
See:
http://support.novell.com/cgi-bin/se...?/10090994.htm
http://support.novell.com/cgi-bin/se...?/10093676.htm
http://support.novell.com:80/cgi-bin...?/10091089.htm
Regards
Rolf Lidvall
Swedish Radio (Ltd)

Novell client for linux - scripted install and configure

the novell client is included in SLED11 SP1
the configuration files are in /etc/opt/novell/ncl (esp login.conf)
I want to script the configuration of the novell-client. Some of the things the interface yast - Novell client does, is:
modify /etc/pam.d/gdm
create /lib/security/pam_ncl_autologin.so
... and maybe more....?
according to Novell Documentation there should be a make_novell-client-conf_rpm Bash script but i cant find it in any of the recent clients (download) nor on the SLED installation.
I think just copying pam.d files and the .so file will work, but might cause troubles in the long run.
What should i do to create these by script?

Originally Posted by lowalcohol
assuming this will do the same as installing it from yast - software, the client is not configured (tree, context, slp) and lacks key files such as /lib/security/pam_ncl_autologin.so needed for integrated login.
/lib/security/pam_ncl_autologin.so is updated by the post processing inside the rpm's. We don't need to do anything. however there is much to do. i'll show what i do. You need to change the variables and entries to suit your env.
create a repo on a build server using the following in fstab
Code:
/srv/www/htdocs/iso/novell-client-2.0-sp2-p2-sle11-i586.iso /srv/www/htdocs/novcli2.sp2/i586 iso9660 user,auto,loop,uid=30,gid=8 0 0
/srv/www/htdocs/iso/novell-client-2.0-sp2-p2-sle11-x86_64.iso /srv/www/htdocs/novcli2.sp2/x86_64 iso9660 user,auto,loop,uid=30,gid=8 0 0
add a repo to the install
zypper -n ar --refresh http://build/novcli2.sp2/$PROC "Novell client 2"
add in bits for ldap
Code:
cd /tmp
wget $WEBPATH/ldap.tbz2
if [ -s ldap.tbz2 ]; then
cd /
tar xjvf /tmp/ldap.tbz2
cd /tmp
fi # if [ -s ldap.tbz2 ];
echo '+::::::' >>/etc/passwd
echo '+' >>/etc/shadow
echo '+:::' >>/etc/group
ldap.tbz2 contains the following after they been changed by 'yast ldap'.
\etc
\etc\ldap.conf
\etc\nsswitch.conf
\etc\openldap
\etc\pam.d
\etc\openldap\ldap.conf
\etc\pam.d\common-account-pc
\etc\pam.d\common-auth-pc
\etc\pam.d\common-password-pc
\etc\pam.d\common-session-pc
add in the client
Code:
zypper --no-refresh --no-gpg-checks -n in -l -t pattern novell-ncl
#lock the files to protect them from future 'zypper dup'
zypper al nici64 novell-client novell-client-script novell-konqueror-plugin novell-nautilus-plugin novell-nmasclient novell-novfsd novell-qtgui novell-ui-base novell-xplatlib novell-xtier-base novell-xtier-core novell-xtier-xplat yast2-novell-client
chkconfig micasad on
configure the client
[CODE]
sed -i s/";net.slp.useScopes.*"/"net.slp.useScopes = FRED, LARRY"/ /etc/slp.conf
sed -i s/";net.slp.DAAddresses.*"/"net.slp.DAAddresses = 10.251.1.99, 10.249.1.99"/ /etc/slp.conf
mkdir -p /etc/opt/novell/ncl
echo Allow_Integrated_Login=true >/etc/opt/novell/ncl/login.conf
echo Default_Tree=XXXXX >>/etc/opt/novell/ncl/login.conf
echo Default_Context=XXX.XXX.XXX >>/etc/opt/novell/ncl/login.conf
echo Default_Server=servername >>/etc/opt/novell/ncl/login.conf
echo DHCP_Tree=true >/etc/opt/novell/ncl/protocol.conf
echo DHCP_Server=true >>/etc/opt/novell/ncl/protocol.conf
[CODE]
(reboot)
These are files installed during build stage, but are used when the client logs in.
in /etc/skel/.novell/ncl, i have a copy of StartupLogin.conf as StartupLogin.conf.new
this file has information in it, but it will be wiped.
in /etc/skel/.kde4/Autostart/logon.sh, i have
Code:
if [ ! ~/.novell/ncl/StartupLogin.conf.new ]; then
mv ~/.novell/ncl/StartupLogin.conf.new ~/.novell/ncl/StartupLogin.conf
FDN=`ldapsearch -x -h 10.251.1.99 -b ou=its,o=fca | grep -i 'dn:' | grep -i $USER | grep -iv workstation`
CONTEXT=`echo $FDN | cut -d, -f2- | sed -e 's/ou=//ig' -e 's/o=//ig' -e 's/,/./ig'`
sed -i "s/UserName.*/UserName = $USER/" ~/.novell/ncl/StartupLogin.conf
sed -i "s/FDN.*/FDN = $FDN/" ~/.novell/ncl/StartupLogin.conf
sed -i "s/Context.*/Context = $CONTEXT/" ~/.novell/ncl/StartupLogin.conf
sudo /bin/update_login.conf.sh $CONTEXT
fi # if [ ! ~/.novell/ncl/StartupLogin.conf.new ];
/bin/update_login.conf.sh has the following and has '%users ALL=(root) NOPASSWD:/bin/update_login.conf.sh' added to /etc/sudoers
Code:
if [ ! -z "$1" ];then
sed -i "s/Default_Context=.*/Default_Context=$1/" /etc/opt/novell/ncl/login.conf
fi
So far this is working well.
The novell login needs to be run once, and on the advanced tab, have the session saved. This then auto runs afterwards for each logon.
as a troubleshooting tool, I :
Code:
cp /etc/etc.1
rsync -avP etc* my-pc:/tmp/
i can then use krusader to compare files (on my-pc), but most importantly, after doing something (eg yast ldap). rerun the rsync line and and it will tell exactly which file(s) changed, so you know which ones to check/keep/alter/etc
hope this helps.
ph

Novell Client 2 after sysprep

During my image process I have sysprep run a batch file which installs several programs. Included are the Novell Client 2 (2nd to last install) and the ZAA (last install). Everything seems to deploy correctly and the system reboots. What I have noticed is that the Novell client doesn't not default as the primary login shown. The system seems to want to boot into windows automatically and throws up a ZAA login dialog.
Did I miss a registry setting that would cause this? The client should autosetup the tree/context/server but even that seems to be missing.
Thanks
Rich

Originally Posted by rhuhman
During my image process I have sysprep run a batch file which installs several programs. Included are the Novell Client 2 (2nd to last install) and the ZAA (last install). Everything seems to deploy correctly and the system reboots. What I have noticed is that the Novell client doesn't not default as the primary login shown. The system seems to want to boot into windows automatically and throws up a ZAA login dialog.
Did I miss a registry setting that would cause this? The client should autosetup the tree/context/server but even that seems to be missing.
Thanks
Rich
why not just have the client on the image itself? we originally had it as a layer, but then added it to image with zen agent to speed things up a bit.

Novell Client help

I just finished setting up my tree in edirectory and Imanager. I installed Novell Client and when I went to login it said the tree couldn't be found.
It is frustrating because I don't know what's wrong.

The Novell Client installation after eDirectory may have broken eDirectory
if it's all on windows. eDirectory uses a new version of NICI, and the
Novell Client may still ship with an older one. Also, the Novell Client
typically installs NICI in client mode (of course) where eDirectory
requires it to be in server mode, and while the client can live in server
mode, the server cannot run in client mode.
I won't bore you, again, with my comments on platform choice. You're in
for a ride as you can see.
Hopefully you're in a VM and can revert a snapshot. Otherwise you may
want to call support to see if they can help fix this. There may be a TID
by now on this, but I haven't seen one lately. You may be able to
reinstall eDirectory, but on windows the eDir install both installs the
binaries that run the service as well as configure a tree, so you may need
to recreate the tree for this to work.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Novell Client OpenSuse 10.3

I am trying to use the Novell Client with Opensuse 10.3.
I followed the coolsolutions "patch" and everything loads as it should. I
get the novell client login box but when I try to login it gives a
security error message:
"Novell Security Message
Cannot access tree " <<displays our tree>>".
I can browse the trees from Advanced but when I try to browse contexts it
displays the same error message.
I have tried to have a look through this area but can not find a suitable
solution. I have disabled the firewall (temporarily - while trying this).
I have CASA enabled, I have OpenSLP setup and running.
Am I missing something obvious?

Oh yes... I'm having the same problem. I BELIEVE if you use Konqueror it works. I haven't tried recently but last time I tried it worked fine in Konqueror.
My larger issue is when I shut down, it hangs at the point of trying to unmount all the mounts. I only get the hang when the novfs module unloads without error (which is rare).
There is something on bugzilla about this but I haven't seen any updates on when it will be fixed.
Originally Posted by Joshua Bergland
On Wed, 16 Jan 2008 18:11:24 +0000, Andy wrote:
> I am trying to use the Novell Client with Opensuse 10.3.
>
> I followed the coolsolutions "patch" and everything loads as it should.
> I get the novell client login box but when I try to login it gives a
> security error message:
>
> "Novell Security Message
>
> Cannot access tree " <<displays our tree>>".
>
> I can browse the trees from Advanced but when I try to browse contexts
> it displays the same error message.
>
> I have tried to have a look through this area but can not find a
> suitable solution. I have disabled the firewall (temporarily - while
> trying this). I have CASA enabled, I have OpenSLP setup and running.
>
> Am I missing something obvious?
I got around this by putting my full context in the user field.
The real problem I am having with the client on 10.3 is that it tells me
my mapped drives have no free space when I try to write to them. Anyone
else having this issue?
Josh

Novell Client 10.3

I have followed the instructions on previous threads to install the
Novell client on openSuse 10.3
http://www.novell.com/coolsolutions/tip/19968.html
I also went to the below link and received the latest novfs and
downloaded it to my desktop and right clicked on it and had yast install.
http://ftp.suse.com/pub/suse/update/...1-3.1.i586.rpm
My novell client now comes up without any errors. Initially when I
entered the advanced tab and clicked on Tree I was asked to configure
SLP and or the firewall which I did. Now I can search for the tree and
select it and I can search for a server and select a server without a
problem. But when I click on Context under the Advanced tab I receive a
"Novell Security Message, Cannot Access Tree". So basically since I
cannot enter in my context I cannot login. I tried putting it my
username, ie. doej.users.tree but this did not work either. I turned
off my firewall to see if this had anything to do with it and that made
no difference.
Any ideas?
Andy

Originally Posted by Andrew Knoke
I have followed the instructions on previous threads to install the
Novell client on openSuse 10.3
Cool Solutions: Installing the Novell Client for OpenSUSE 10.2 onto OpenSUSE 10.3
I also went to the below link and received the latest novfs and
downloaded it to my desktop and right clicked on it and had yast install.
http://ftp.suse.com/pub/suse/update/...1-3.1.i586.rpm
My novell client now comes up without any errors. Initially when I
entered the advanced tab and clicked on Tree I was asked to configure
SLP and or the firewall which I did. Now I can search for the tree and
select it and I can search for a server and select a server without a
problem. But when I click on Context under the Advanced tab I receive a
"Novell Security Message, Cannot Access Tree". So basically since I
cannot enter in my context I cannot login. I tried putting it my
username, ie. doej.users.tree but this did not work either. I turned
off my firewall to see if this had anything to do with it and that made
no difference.
Any ideas?
Andy
I am having this same problem except on 11.2 running the ncl sp2
Any help would be greatly appreciated.
thank you
-ryan

I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but th

I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

If you are searching the registry, check for the "Senforce" string. It should be at HKLM\Software\Senforce
Try running the install program for the ZSC with the following command line:
setup.exe /V"STUNINSTALL=1"
If you've specified an uninstall password, try this one instead:
setup.exe /V"STUNINSTALL=1 STUIP=password"" (please note the double quote at the end)
Let me know if that helped you.
Daniel
>>>
From: Andy_DeWees<[email protected] du>
To:novell.support.zenworks.endpoint-security-management
Date: 2/5/2009 12:52 PM
Subject: I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but the login prompt did not appearfor ESM client or the icon was not in the systray. Everything seems towork, besides at times (a couple times today) it terminates his ethernetcard/connection. I would re-image his computer but he has severalapplications and
I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

Windows 7 Client 'sees' an old version of windows 2012 server share

Hi All,
I have a problem which seems to be a common theme looking at other threads. Here's the overview of the problem:-
I have multiple windows 7 clients and a windows 8.1 client within a 2008 Server in a domain.
I also have a Windows 2012R2 Server which is not joined to the domain. There is a Share on the 2012R2 which has the Caching Option turned off. Everyone full control on Share & File permissions.
One of the Windows 7 machines in Explorer when it looks at
\\2012server\share sees an old version of the folder. It seems that SMB 2 chaching is working too well. Not even pressing F5 or clicking View, Refresh updates windows explorer.
It took a reboot to get the workstation to see the up to date contents of the share on the 2012 server.
We don't seem to have that behaviour with that client against the 2008 server.
I have seen this behaviour on another machine un-related to us at another location which was in a workgroup with a 2012 server and no domain.
Questions:-
Is there some sort of problem with Windows 7 workstations working against 2012 Servers in a non-domain setting or is it just Windows 7 against 2012 servers period?
I understand that Windows 7 utilises SMB1 & SMB2. SMB2 introduced caching. If the server has turned off the share cache option should the client cache the contents of the share or the information about the files & folders & 'file not found'
information?
I want to open a file handle to a file on a network share so I can read and write data to it. But I also want to know that when I look at the folder to open the file I'm actually looking at the live version of the folder and files in the folder and
not a cached version of the folder. If it's a cached version the file might be there already but I won't see it.
Is there an API call that tells the client to get a fresh view of the server share so I can be absolutely sure that when I look for a file on the server I'm getting the correct answer and not one from cache.
I first posted the question with the same subject "Windows 7 Client 'sees' an old version of windows 2012 server share" in the Windows 7 Networking Fourm
https://social.technet.microsoft.com/Forums/en-US/23bf3627-987b-4c27-8062-85a284a2cda4/windows-7-client-sees-an-old-version-of-windows-2012-server-share?forum=w7itpronetworking and it was suggested I repost in here. Please do take the time to read
the thread which will save time with suggestions that have already been covered.
As the computers that can be affected by this problem are not mine I cannot enforce or guarantee that any of my 'client base' will apply any hotfixes. I will also not have the ability to tweak registry settings as I can't guarantee Admin Access.
It seems that we need to go back to SMB1 as all the tweaks to SMB since those days have introduced problems with the basic requirement of sharing files from a share on a server for Read/Write purposes. I have tried turning a network back to SMB1 and that
has resolved a lot of the issues but then I found a post/MS blog that states not to leave the network on SMB1
The Caching option of the share had already been turned off. Surely Windows clients should not cache any information about the share but I think that is not the case.
Thanks is advance
Robert

Hi Shaon,
Thanks for looking into this.
If this is a known issue, why isn't the hotfix rolled into a general windows update if this is a known problem? However this doesn't just affect domain joined workstations.
Surely it's basic functionality for a networked computer to access files and folders on a network file server. It's what networks were invented for at the end of the day.
I am unable to apply hotfixes to these computers that are having the problem due to the fact they are not mine but my customers.
At one of my customers sites I disabled SMB2 from the server and network clients as well as disabling the network adapter power saving option. This seemed to resolve the issues that I saw on one client that seemed to be 30 minutes behind the rest of
the network. The hotfix you link to states that it is for Domain joined computers. At my customer site the PC's are not in a domain at all, just a workgroup with workstations and a 2012r2 server. Will the hotfix be applicable to non-domain machines?
Also many clients seemed to loose the file handle to an open file on the server. I'll get them to turn SMB2 back on at some point after I send out some updates but all the problems I see seem to be caused by the caching functions in SMB2. SMB1 is good and
stable. It's SMB2 that seems to be causing the problems as it was designed from the ground up for caching.
Has this networking issue been resolved in Windows 8, 8.1 and 10?
As I am unable to apply a hotfix to 1000's of PC's that are not mine, is there an API call or something where I can get the windows client to stop lying and get me the current state of a folder on the server?
Will Turning off ClientSideCaching fix the issue? HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
CSCEnabled
Or will every machine need to be tuned individually according to the following guide:-
https://social.technet.microsoft.com/Forums/windowsserver/en-US/7bd9978c-69b4-42bf-90cd-fc7541ccb663/forum-faq-troubleshooting-network-file-copy-slowness?forum=winserverPN ?
Robert

CSA & Novell Client

We run a Novell network and our primary authentication client is the Novell client. I've setup CSAMC v6 and have been tuning for the past couple of days.
I seem to have a problem with the Novell client login script. Whenever I login, the search drives don't map. I get:
FS-TBRHSC-ZEN
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[ROOT S16:=Z:=FS-TBRHSC-ZEN\SYS:PUBLIC]
The error code was 8884.
I've opened up TCP/524 and TCP/427 to all of our Novell servers with no results. I thought it might be ephemeral ports to I opened them up as well.
This is really frustrating the heck out of me. Does anyone have a solution?
Ryan

I have tuned Novell in CSA 4.0, and upgarded the rules to 6.0 and they seem stable. Please e-mail me at dhudson at hanover dot com, and I will send you na export of my Novell tuning...

Novell Client for Linux 2 beta & VMWare - bridged only?

OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
OpenSUSE is installed as a VMWare Workstation guest using NAT. When attempting to use contextless login, the Novell Client hangs. If you disable contextless login and then browse to the right context, you can login OK.
If you change the virtual NIC from NAT to Bridged, contextless login works fine. If at all possible, we need to use Bridged instead of NAT (long story).
Any idea what could be the problem? From what I can tell, SLP, DA, etc are set correctly, but I could be wrong.
Thanks.

Originally Posted by Thorsten Kampe
* mlazovjp (Mon, 14 Dec 2009 18:56:02 GMT)
> OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
>
> OpenSUSE is installed as a VMWare Workstation guest using NAT. When
> attempting to use contextless login, the Novell Client hangs. If you
> disable contextless login and then browse to the right context, you can
> login OK.
>
> If you change the virtual NIC from NAT to Bridged, contextless login
> works fine. If at all possible, we need to use Bridged instead of NAT
> (long story).
>
> Any idea what could be the problem? From what I can tell, SLP, DA, etc
> are set correctly, but I could be wrong.
Use NAT only if you need NAT - otherwise use bridged.
Thorsten
I was afraid that someone was goign to say something like that :)
We use port security hardware on our network, which will disable a port on the switch if it detects multiple MAC addresses on the same port. A virtual machine's bridged networking sets port security off and disables the port, so we have had to resort to NAT for all virtual machines. We can ask for exceptions to be made for a subset of our lab computers, but that is not an ideal solution.
Not only is that extra overhead for us to manage these exceptions, but we will not be able to realize our long-term goal of providing the virtual machine to our students to use on their personal notebooks since we cannot provide them port security exceptions.
I am still having problems grasping the reason that a contextless lookup (via LDAP, I assume) would misbehave while coming from a NATted connection but a bridged connection works fine on the exact same virtual machine. Shouldn't the communication between the VM and the LDAP server work properly either way??

Windows 7 with MDT - Novell Client / Zen Agent?

Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!

Originally Posted by joebrug
Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!
You can use this during your sysprep process that way it does not matter if it is installed or not.
zac fsg -d
:: THIS WILL ALLOW A NEW GUID TO BE CREATED IN ZEN AFTER REIMAGING
del "C:\Program Files (x86)\Novell\ZENworks\conf\deviceguid"
del "C:\Program Files (x86)\Novell\ZENworks\conf\devicedata"
del "C:\Program Files (x86)\Novell\ZENworks\conf\*.sav"
del "C:\Program Files (x86)\Novell\ZENworks\conf\Guid.txt"

WWW Location of the Novell Client for XP supporting IP Gateway Services

When connecting Windows XP workstations to the SBS 6.0 server through the
Novell Client 4.9SP1a for Windows XP, there are no services within 4.9
for IP Gateway included. As many of you know, by using BorderManager as
the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
accessing the Internet need the IP Gateway service installed with the
client. The Novell Client CD-ROM shipped with the Novell SBS 6.0 media
has clients for Windows NT/2000 (outdated) but none are compatible for
Windows XP (it appears that Novell had not updated their Novell SBS 6.0
media since they started shipping it). In addition, the online
documentation included with the media is outdated (e.g. BorderManager 3.6
docs for BorderManager 3.7 being shipped) and do not mention anything
about configuring Windows XP clients for Novell IP Gateway services.
I have thoroughly looked within Novell's Support site the past few weeks
for:
+ The original Novell Client 4.9 (prior to support packs) to see if that
version of the client has IP Gateway services included (file not found or
listed).
+ Previous Novell Clients for Windows XP to see if those versions support
IP Gateway services. (Support Pack versions only are listed, but no
original versions, and do not contain Novell IP Gateway services).
+ Any instructions or tips for configuring the Novell IP Gateway services
within the Novell Client 4.9 or earlier versions for Windows XP(documents
are non-existent).
All of the above leads the following question:
Can someone please direct me to the location to where the proper
Novell Client for Windows XP supporting Novell IP Gateway services?
Since Windows XP has been around for a few years now, one would think
Novell would have developed a client for it that possesses Novell IP
Gateway services by now to be used with BorderManager. Correct? If so,
where is it? In addition, one would think Novell would include the media
supporting the current software they are shipping, not outdated ones.
(Or at least, ensure their outsourced sales services are doing so.) In
addition, one would also think Novell would at least provide the
necessary tools/files necessary to at least to have the ability to
install their products out of the box - instead of forcing their
consumers to purchase unnecessary additional support services for
something they should have included within their media package or website
at the start.
Nevertheless, I appreciate any input where to find the appropriate Novell
Client for Windows XP supporting Novell IP Gateway services.
Thanks,
EricV

In article <cb60c.5596$[email protected]>, wrote:
> As many of you know, by using BorderManager as
> the Firewall/NAT/IP/IPX Gateway to access the Internet, all workstations
> accessing the Internet need the IP Gateway service installed with the
> client.
>
This is simply not correct. Novell has not been providing IP gateway
functionality within Client32 for a long time, because it is not needed,
and it had serious limitations.
I haven't had a client using IP Gateway for many years now, and I have a
*lot* of BorderManager clients.
The alternative to IP Gateways is a combination of proxies and NAT w/filter
exceptions.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Installing Novell Client fails due to 'untrusted signer'

I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?

Originally Posted by vatson
I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?
You need to install the newest client (that have a never certificate) on a device and then export it from that machine, after that you import it on the devices you want to install the client before running setup.exe.
Thomas

Novell Client sees no trees

Similar Messages

Maybe you are looking for