Solved

Mounting NT4.0 from WfW problem

Posted on 1997-11-03
3
240 Views
Last Modified: 2013-12-23
We have implemented an NT 4.0 server with WfW 3.11 clients.
When we want to add a networkdrive from file manager in WfW we can see our NT server, but when we want to select him to select a shared device or folder we get "LAN MANAGER ERROR" message.  I can mount a shared device or folder
under DOS as an extra drive, but then I lose too much lower memory.
I did find the following workaround.  When I try to mount the network drive from the WfW client I don't click on the NT server in the list, but I fill out the name of the server and the correct path in the field PATH.  So I assume the problem is that I cannot get a proper overview of the
available directories.
The same thing happens when I want to rerout the LPT1 port on the client to the server.  The workaround works here as well.
Can someone give me a better solution than this workaround?
0
Comment
Question by:wilfrieds
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 4

Expert Comment

by:TimCaturaHouser
ID: 1567143
It has been a long time since I have worked the 3.x side..... under your networking, have you found the panel that talks about ghosted connections? On the same panel is a x box for connecting to NT..... I think that may fix you.
0
 
LVL 5

Expert Comment

by:y96andha
ID: 1567144
What happens if you use the net use command from a dos prompt in windows, with the windows drivers? Are you using the IPX protocol? If so, there is a registry change needed when servicepack 3 is installed for it to work with non-NT clients.
0
 

Accepted Solution

by:
kreardon earned 100 total points
ID: 1567145
This problem is caused by having a share with a name longer than
8.3 on the NT 4.0 server. WFWG workstations will not let you
browse the server and will display the lan manager error. Make the share names shorter on the NT box, or map to the drives directly from WFWG using the share name and not browsing.
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How to scan rdp  ''only'' open port 3333? 5 172
Independent domain networks for setup 6 128
Linksys 4 port wireless router 62 72
can i use this ip range for my company 3 48
Sometimes you might need to configure routing based not only on destination IP address, but also on a combination of destination IP address (or hostname) and destination port number. I will describe a method how to accomplish this with free tools. …
An article on effective troubleshooting
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

742 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question