NET command

  • Thread starter Thread starter steve k
  • Start date Start date
S

steve k

In past used NT4 and dos floppy to do backups using NET command.
Something like
net start basic
net use c: \\lazio\dumpspace

and as long as I had permissions set correctly everything worked just fine.

Now however, using XP these commands do not seem to work correctly. I
'net' no longer used on XP? Has the systax changed?

Any help?

TIA
 
In past used NT4 and dos floppy to do backups using NET command.
Something like
net start basic
net use c: \\lazio\dumpspace

and as long as I had permissions set correctly everything worked just fine.

Now however, using XP these commands do not seem to work correctly. I
'net' no longer used on XP? Has the systax changed?

Any help?

TIA
Click to expand...

Steve,

The "net" command works fine for me. Can you provide some examples of your
commands used, and the exact errors? Try pasting the complete command and
response, redirected:
<http://nitecruzr.blogspot.com/2005/06/command-window.html>
http://nitecruzr.blogspot.com/2005/06/command-window.html
 
This is the DOS net command. Hers are commands and responses

net initialize /dynamic
The command completed successfully.
netbind.com
MS-DOS Lan Manager V2.1 Netbind
tcptsr.exe
Microsoft DOS TPC/IP 1.0a
tinyrfc.exe
no response
net start basic
Type your user name, .......
Command completed sucessfully.
net use \\lazio\sfk
Error 3652: This command is only available on enhanced workstations.

Now this same "net use" works fine from one XP to another. But as stated
it used to work on NT workstations 4.0 and NT server 4.0. Currently
using the NT workstation for above documentation. If I change the XP for
a NT4 workstation or server it works fine.
 
Chuck wrote:
This is the DOS net command. Hers are commands and responses

net initialize /dynamic
The command completed successfully.
netbind.com
MS-DOS Lan Manager V2.1 Netbind
tcptsr.exe
Microsoft DOS TPC/IP 1.0a
tinyrfc.exe
no response
net start basic
Type your user name, .......
Command completed sucessfully.
net use \\lazio\sfk
Error 3652: This command is only available on enhanced workstations.

Now this same "net use" works fine from one XP to another. But as stated
it used to work on NT workstations 4.0 and NT server 4.0. Currently
using the NT workstation for above documentation. If I change the XP for
a NT4 workstation or server it works fine.
Click to expand...

Steve,

The "net" command under Windows NT / 2000 / XP works fine in its own context,
though it may not work exactly as it did under any previous version.

Why not tell us what you want to accomplish, or what your overall problem is,
rather than what you want to do right now?
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html
 
If you are trying to map a drive letter, it cannot be C: as that's reserved
for your local drive.
net use X: \\lazio\dumpspace (for example) should work fine. If you have a
further problem, open a command prompt and execute it there (rather than
with a run command) so you can see the result message. If it fails report
back with the exact error message.
 
Sorry, thought it was obvious. As noted by GTS I am trying to map a
drive on an XP system.

This is being done to make an image copy from a NT4 workstation to copy
it to an XP system.
 
The C: was a copy mistake, sorry. Ran the programs and received the
following error.

Ran net use g: \\lazio\images on NT4 system and got

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

Ran net view on NT4 system and got error:
Error 6118: The list of servers for this workgroup is not currently
available.

Ran same net view command on XP machine and got

Server Name Remark
\\CAMPANIA campania
\\LAZIO
The command completed successfully.

So it seems that net commands work fine on XP but not on NT4 systems.
They do and have worked fine on NT4 system but seems not compatable with XP.
 
STOP THE TRAIN. AN IDIOT HAS TO GET OFF!!!!

I hate to say it, but, the problem is mine. I don't really want to
explain but I owe it to you helpful folks. I have two NIC's on the
laptop and the one I use for process was unhooked. All I can do is
"Pardon me please".
 
STOP THE TRAIN. AN IDIOT HAS TO GET OFF!!!!

I hate to say it, but, the problem is mine. I don't really want to
explain but I owe it to you helpful folks. I have two NIC's on the
laptop and the one I use for process was unhooked. All I can do is
"Pardon me please".
Click to expand...

Well, physical connectivity is the basic issue that has to be resolved. Glad
that it was that simple. Thanks for updating the thread.
 
No problem. We've all had those moments :)
--

steve k said:
STOP THE TRAIN. AN IDIOT HAS TO GET OFF!!!!

I hate to say it, but, the problem is mine. I don't really want to
explain but I owe it to you helpful folks. I have two NIC's on the laptop
and the one I use for process was unhooked. All I can do is "Pardon me
please".
Click to expand...
 
Back
Top