IT Employment

General discussion


Using the command line to navigate the network

By azul ·
I have a network of 6 pc's. I am trying to use the command line interface to view drives and files on networked computers.

3 of the computers are WXP, one is W Server 2K3. Currently all the machines are in a workgroup but I will soon have a domain setup.

I found a way to do this in the past but have forgotten how and no longer have the link to the page I found this on. I remember that it was used in conjuction with the "pushd" command.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -


by entawanabi In reply to Using the command line to ...

It is one of the rudimentary things: for a lot of reasons 'THEY' could no longer be networked together correctly. It is a place to start.

Collapse -

I am sorry,

by azul In reply to MAYBE?

I mean no offense, but your post is incoherrent.
Are you drunk?
Did you mean to respond to a different post?
Do you understand the question?
What on earth are you talking about?

I am looking for a way to do at the command prompt what I can already do, just fine and with out issue using windows explorer.

Collapse -

No offence taken, i'm not a good liar!

by entawanabi In reply to I am sorry,

"For a lot of reasons your computers may no longer networked together properly if they ever were" I think that is about correct, It is a simple posit Have you checkked, Just because you wired them together does not mean they are networked together, especially if they are more than one type of operating system that may not be compatible.

Finally just because you are a drunk does not mean that anyone else also does this in there cups as you do!

Collapse -

Basic troubleshooting

by JamesRL In reply to No offence taken, i'm not ...

Azul has already mentioned that these computers are networked together and that through the Windows explorer these computers can see the shares on the other computers.

Therefore a) they were networked together properly, and b) they are networked together properly.

Azul simply asked for some help with an obscure command at the DOS prompt, he didn't say there was an issue with the network itself.

I understand his frustration.


Collapse -

Careful James

by jdclyde In reply to Basic troubleshooting

Max is going to come down on you, HARD!

MAn, I LOVE your two possible solutions! :^O

Collapse -


by Jaqui In reply to Careful James

they were 2 distinctly different statements.

Collapse -

For those who read fast

by JamesRL In reply to HEY!!!!!

I should have used italics on "were" and "are".

I've learned alot in 20 years of messing with computers. I should write a book and title it, "First check the power cable".



BTW did you check out:

I was actually good. Despite the tone is more:this is how it is, correct? than - how does it work.


Collapse -


by jdclyde In reply to HEY!!!!!

you did just fine. Sometimes it just has to be said and you were in the right place at the right time!

Collapse -


by noyoki In reply to No offence taken, i'm not ...

> Finally just because you are a drunk does not mean
> that anyone else also does this in there cups as
> you do!

Cups? He didn't mention Linux I don't think, so why would he need cups? ]:)

Collapse -

Two possibilities

by faradhi In reply to Using the command line to ...

If you have not disabled the server service on the PCs you can use the administrator share to browse using explorer.

Otherwise, you could try PSEXEC from This will allow you to perform any command line command remotely.

Related Discussions

Related Forums