Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

map drive to netware volume in dos

Status
Not open for further replies.

Davo67

Technical User
Jul 3, 2001
17
GB
i'm trying to map a drive on a dos client to access a legacy dos application to a netware 5 volume.

I get it to logon using NET LOGON etc. which works

when i use NET VIEW \\meridian i can see all the volumes and print queues.

I am trying to use

NET USE F: \\meridian\data3

(data3 being a volume which has the dos app. and is listed when doing NET VIEW)

I get the following error

ERROR 53: The computer name specified in the network path cannot be located.

Any help would be greatly appreciated ;O)
 
This could be difficult to do, infact I'm not too sure if you can. Using a DOS box on an NT (and above) Workstation, you can use NET USE in conjunction with the /USER switch to specify the NDS context. In DOS, however, you do not have that facility.

Firstly, does your server MERIDIAN have a R/W (or Master) replica of the partition where your user object resides? If so, do you have a bindery context set to this? I would have thought that any connection via this sort of method would be a bindery connection rather than an NDS connection. Saying that, your user and password on the DOS client (I presume that is configured in the INI files?) will have to match that on your Novell user.

Can't you run this on a W2k Workstation in DOS? Would be a far better/easier way of working? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Thought: why are you using Microsoft methods of connections rather than the Novell DOS Client? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
The DOS Client on an NT 4 is NOT DOS - many DOS applications will not work properly in this environment. All those NET commands you mentioned are not DOS commands - they were introduced by Microsoft within NT and will attempt to create IP connections. Even if you can get a persistent connection to work (highly doubtful, I don't see it happening), if you run a DOS Client in an NT DOS window, you'll not get the Novell DOS client to work properly (I am assuming you're already connecting the computer via MS NetBIOS and MS IPX - hence the ability to "see" anything and resolve "\\meridian" as something of significance). As 'TheLad' mentioned in an afterthought - use Novell DOS client commands to do the connecting and boot the computer completely as DOS using real MSDOS 6.22 or Caldera's latest DRDOS. I would suggest making a bootable floppy with all the connectivity instructions you'll need and I hope that the NT you're running this on wasn't formatted as NTFS (otherwise, you'll have problems accessing any of the files on this computer's hard drive(s)).

My 2 cents on NT DOS...

P-Dawg
 
TheLad & PrairieDog

Many thanks for your comments. You've provided with a much better understanding of Novell/NT networks for a complete newbie (less than 2weeks..).

I've fixed the problem. I was using a Novell dos client but I think the files were old. I've downloaded a later version which was hidden/buried in the Novell site, which i found from a google search rather than Novell and that worked.

Sorry to have wasted your time but your comments have helped me greatly and it's always useful getting advice from the experts.


 
Hey, no time wasted here. No question is ever a waste of time! Keep posting if you have problems! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top