Solved

NT Networking question

Posted on 1997-09-11
2
787 Views
Last Modified: 2013-12-23
While connection as an administrator, if I try

C:\>net view \\kampot
Shared resources at \\kampot

Share name   Type         Used as  Comment

------------------------------------------------------------
DISKC        Disk
HPLaserJ     Print                 HP LaserJet 6P
The command completed successfully.


c:\>net use i: \\kampot\diskc
System error 53 has occurred.

The network path was not found.

(I have granted all permission to the diskc share name)

I remember, long time ago with previous version of NT, this was working and
should still work.

I have NT 4 SP3, standalone computer (no serveur, workgroup is workgroup)
netbeui and tcpip protocol loaded. RAS is configured through ISDN but not started
When I browse through explorer, I did not see my own computer in the workgroup

if I start RAS, I get the following error :

c:\>net use i: \\kampot\diskc
System error 1214 has occurred.

The format of the specified network name is invalid.

strange no?
0
Comment
Question by:nissakid
[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
2 Comments
 

Accepted Solution

by:
rommel091097 earned 0 total points
ID: 1565549
Are you trying to mount the entire drive C?

If so, the following will work:

net use i: \\kampot\c$

Substitute different letters depending on the drive you want to connect.

--Rommel.

0
 

Author Comment

by:nissakid
ID: 1565550
The problem is solved but I did not find a way to poste it here.
The problem was a little more complex :

in the network, the netbeui was defined and is started. That is why the NT computer is responding to the request.

But, the binding section was corrupted , the netbeui has disappears. I dont know why.
The solution was to delete all the configuration, restart the computer and them, redefine every piece of the network, tcpip & netbeui.

Delete everything is necessary,  because just deleting netbeui and redefining it is not enough.

Also, this will work ONLY if you re-appy the NT service pack
that was installed before.
Else, NT , at startup will report error message not related to the problem.

Again, the problem has been solved
0

Featured Post

Enroll in June's Course of the Month

June's Course of the Month is now available! Every 10 seconds, a consumer gets hit with ransomware. Refresh your knowledge of ransomware best practices by enrolling in this month's complimentary course for Premium Members, Team Accounts, and Qualified Experts.

Question has a verified solution.

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

This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
Resolve DNS query failed errors for Exchange
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

705 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