CMD not working

[FirstNick]

Hi,

This is my first post, so sorry if its in the wrong place or something like that .

In CMD I would like to use the following command:

route ADD 82.211.0.0 NETMASK 255.255.0.0 192.168.0.1 MATRIX 3 IF 8

But CMD does nothing!

When I try route PRINT it does the same:

C:\Windows\system32>route PRINT
C:\Windows\system32>

I can use ipconfig and PATH:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\QuickTime\QTSystem\

I am the Admin and I start CMD with admin rights in Vista Home Premium.

I hope that someone out there can help me.

Thank you!

Best regards

Nicklas L.

 

[richc46]

So that I or someone else can give you the best answer.

Do you type cmd, in search. Then right click and indicate run as administrator?

If not, how do you access the cmd prompt?

 

[FirstNick]

I type CMD in search then right click and choose run as administrator.

Thank you for your reply

 

[richc46]

Lets see if CMD is actually working:

Type this: ipconfig. Just that nothing else. Did it work? Dont use run as administrator.

 

[richc46]

If the above works try this in CMD and

Run as administrator, type this, sfc /scannow.

This is a two pronged test. We will be testing CMD, if it does work, tjhis time, any corruption in the system will be corrected. If it does not work, we have to try to resolve the problem.

 

[FirstNick]

ipconfig is working when I run CMD both with and without admin rights .

When I run sfc /scannow it tells me that it found damaged files, but was unable to repair all files.
It tells me that I can find more information in CBS.log, but when I try to open the file a window pops up and tell me "Access denied"?

Again, thank you for your reply

 

[richc46]

Things are not as bad as they look. SFC, may work, it is a good feature of Vista. Its downside is that it fixes one file at a time. Try it 2 more times. After the second try, tell me what it reports. We will go from there.

So at this point, your only problem was that you could not use the commands as mentioned in the first post?

What are you trying to accomplish with your commands? Printing to a network printer?

Did the command every work?
If yes, did something happen prior, which may have caused the problem?

 

[FirstNick]

I tried SFC 8 times, but it still says the same and when I try route PRINT and route ADD 82.211.0.0 NETMASK 255.255.0.0 192.168.0.1 MATRIX 3 IF 8, it does the same as described in the first post.

I am unable to use "route PRINT" and "route ADD" , but I am having no trouble with ipconfig.

I live in a dormitory and in order to access the Internet I have to logon to their servers. No problem there. But when I try to establish a VPN connection I get cut off the from the servers and thus the Internet and the VPN connection is lost.

A friend helped me with the problem giving me the codeline "route ADD 82.211.0.0 NETMASK 255.255.0.0 192.168.0.1 MATRIX 3 IF 8" It worked the first time, but when I rebooted the PC the CMD would not work as descried early.

I am afraid that I do not recall any incident prior.

Thank you very much for the answers!

 

[richc46]

Can you try using system restore and going back to when it worked?

 

[FirstNick]

No, not a option I am afraid - it is too long ago.

 

[hotajanmejaya]

ipconfig is working when I run CMD both with and without admin rights .

When I run sfc /scannow it tells me that it found damaged files, but was unable to repair all files.
It tells me that I can find more information in CBS.log, but when I try to open the file a window pops up and tell me "Access denied"?

Again, thank you for your reply

u can access CBS.log if u change the security permission of CBS.log to "full control" for user

 

[FirstNick]

Hi!

I resolved the issue by erasing the hard drive and reinstalling Windows .

Not the easy way out, but it helped .

Thank you both very much for your help!


The best regards

Nicklas

 

[richc46]

Sorry that the remedy was difficult, but we are glad that your computer is working properly, again.