Sorry I didn't read this before the break.....but you can go to network
properties,
Novell Client properties, Advanced Login tab....scroll to the bottom and
find
the last four settings....workstation only should be "on" not "off".
Hope this helps.

John

"Timothy Leerhoff" SPAMqwest.net> wrote in message
news:rdGlh.22136$jS4.4428@prv-forum2.provo.novell.com...

I agree with Niclas completely.
Don't waste your money on the fastest cpu either.
I usually get the slowest cpu offered which
makes a big price difference.Performance wise,
you won't notice the difference.
-dan denton

Education Technologists,
Please take a moment to follow this link
http://en.opensuse.org/education and join in!
Our goal here is to remove some of the roadblocks to converting your
school to opensource and SUSE linux.
Please feel free to join the mailing list and post a review.
James Tremblay
CNE 3.x, 4.x, 5.x
CLE in training

Can anyone help me.
Whe have the next problem:
A Novell 6.5 network whit Zenworks 6.5 en the clients WindowsXP whit
Cliet 4.91 SP3. The problem is that de clients not allways wil get the
policies whe installed. Its not depending of a user or a computer. Whe
have updated our clients but nothing helps.

Yours

Hei,

By Novell environment, do you mean that the workstations have Novell
Client32 installed or what?

If you remove Client32 from the workstation, does it solve the problems?
Tried it? ..just to see if this has anything to do Novell stuff
actually.

Is Novell Zenworks Management agent installed? It includes its own
management/remotecontrol stuff that might interfere. Although we have
used winvnc, NetOp, pcanywhere and similar.. no probs.

-sk

Hello,

When using the clasroom management software together Novell environment,
we can find two problems:

1. Sometimes classroom management system's (Windows based application)
client software (running as a service) can not resolve the computer mac
address. What is the reason for this? Could this be avoided)

2. Classroom management software in Novell environment can not resolve
the file names and paths the same way as it seems to do in the standard
Windows environment. What could be the reason for this?

Best Regards,
Kimmo

For the sake of my sanity, someone please toss me some help here. We have
a new Wireless system installed in one school building. Excellent
coverage and good network signal strength. It's a Trapeze Thin AP
Wireless setup going back to a MX-216 controller. Novell server is 6.5.
It is the student application server, and DHCP server for the network.
Wired through the network, no problems at all. Wireless authentication to
the server doesnt work. Have to connect workstation only. I can ping the
server. I get a DHCP address from the server. No tree can be found. Same
laptop connects wired, gets on the tree/server/context without issue.

I've grabbed packets from both sides of the MX-216 controller and it's
forwarding the packets out like it should. I've tried various drivers for
the wireless card, various versions of the novell client, and get the
same results with the Intel Wireless manager, or the windows zero config.
So from what I can gather, the problem is between Novell, and it's
ability to authenticate over wireless. We run WPA and WPA2 with PSK on
TKIP

Help :)

Hi All

We have NDS and an AD (windows 2000), we use DirXML to sync passwords
and useraccounts between the two which works great.

We presently use scripts that "Net Use" drives to the AD PDC and BDC's
and they work fine (i guess as they have no local account capability).
However any other AD member servers will not authenticate our users
that are passed to the server as "username" rather than
"domain/username".

Is there an option that i can set on the server so that it ignores
local user accounts from remote and always checks the domain or at
least prefixes domain\.

I realise this is a M$ issue i am having but novell guys are more likely
to see it.

Many thanks
Julian

Niclas Ekstedt wrote:

ZDM7 software metering licences are still made with nwadmin =)

-sk

Niclas Ekstedt wrote:

Ronny never answered, but I'm curious as we have same problems with
802.1x coming.

Without client32, how do we deploy login scripts?

-sk