General discussion

Locked

Novell's Client for NT 4.8

By bfeltus ·
I have Novell's client for NT on nt4 workstation. I received errors from netwares' container login script, such as server not found, invalid drive mappings. Can map to drives through nt explorer and network neighborhood. Is there a problem with NT and the map command?

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Novell's Client for NT 4.8

by jpt In reply to Novell's Client for NT 4. ...

No there should not any problems with NW client 4.8 and Map commands. We are using that client and do not have an problem.

John

Collapse -

Novell's Client for NT 4.8

by bfeltus In reply to Novell's Client for NT 4. ...

Poster rated this answer

Collapse -

Novell's Client for NT 4.8

by rwscc In reply to Novell's Client for NT 4. ...

I've found the login scripts to be very picky on the syntax. Try using the fully qualified volume names. For example: cn=myserver_sys.ou=myoffice.o=mycorp:\public\ This seemed to clear up most of the mapping problems for us after we started using it on EVERY map command.

Collapse -

Novell's Client for NT 4.8

by bfeltus In reply to Novell's Client for NT 4. ...

Poster rated this answer

Collapse -

Novell's Client for NT 4.8

by GolfKingUK In reply to Novell's Client for NT 4. ...

Do you have a WINS Server(netWare Gateway) setup on the network? I had exactly the same problem, it had to do with the WINS server. Hope this helps.

Ron

Collapse -

Novell's Client for NT 4.8

by bfeltus In reply to Novell's Client for NT 4. ...

Poster rated this answer

Collapse -

Novell's Client for NT 4.8

by alan In reply to Novell's Client for NT 4. ...

I haven't found any problems with the MAP command in container login scripts; however, could you post an example of the MAP command from your script? I only have a couple machines using 4.8 so far and any problems I encountered had more to do with installing the client itself, not with interaction with netware. What was your previous client before using 4.8?

Collapse -

Novell's Client for NT 4.8

by bfeltus In reply to Novell's Client for NT 4. ...

Poster rated this answer

Collapse -

Novell's Client for NT 4.8

by Kevin Anderson In reply to Novell's Client for NT 4. ...

No, there are no issues that I've heard of.

Sometimes people who have problems mapping to an NDS object (MAP y:=SERVER_VOLUME:DIRECTORY) find them resolved if they map through a UNC name (map t:=\\SERVER\VOLUME)

And vice versa.

using netware administrator, check that your NDS volume objects point to legitimate places. If not, delete them, and recreate them. This shouldn't affect your user's rights. running DSREPAIR usually can also correct this.

The fastest solution is usually tochange the map opject though.

Kev.

Collapse -

Novell's Client for NT 4.8

by bfeltus In reply to Novell's Client for NT 4. ...

Poster rated this answer

Back to Networks Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums