General discussion

Locked

Loss of drive mappings - Windows NT Serv

By terrance.grossmith ·
We are running Windows NT Server 4.0 Terminal Server Edition. We have a logon script that maps drives to several different machines through a DFS server each time a user logs on. After about 5-10 logons, the terminal server becomes unable to connect to the remote machines, displaying the following error message: "System error 67 has occurred. The network name cannot be found." This error occurs for every mapping attempt, despite the fact that the remote machines are up and running just fine. A simple reboot of the terminal server corrects the problem temporarily, but then it just happens all over again after another 5-10 logons. It's a continuing cycle.

Does anyone have any clue why this might be happening? Thanks in advance foryour help.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Loss of drive mappings - Windows NT Serv

by calves In reply to Loss of drive mappings - ...

Two things to look into:
Your Wins Server and Your Master Browser.

Good Luck!

Collapse -

Loss of drive mappings - Windows NT Serv

by terrance.grossmith In reply to Loss of drive mappings - ...

The question was auto-closed by TechRepublic

Collapse -

Loss of drive mappings - Windows NT Serv

by PrinterManager In reply to Loss of drive mappings - ...

It?s old you should re-post.

Collapse -

Loss of drive mappings - Windows NT Serv

by terrance.grossmith In reply to Loss of drive mappings - ...

The question was auto-closed by TechRepublic

Collapse -

Loss of drive mappings - Windows NT Serv

by terrance.grossmith In reply to Loss of drive mappings - ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums