how to check the nic settings of another workstation

I suppose you could use remote registry if you have the permissions to open another's registry.

can i do anything using vlans or our cisco infrastructure?

What settings?  Speed/duplex or other?

yes

AH!

We normally look at our Cisco switches and use the command:

show int counter error

This shows:

Align-Err    FCS-Err   Xmit-Err    Rcv-Err UnderSize

If errors show up here, it usually means the NIC is not configured the same as the port - resulting in a duplex mismatch.  This is the closest you'll get to see in the NIC config from the network.

A really helpful short cut is to turn this into an alias command like this:

alias exec see show int counter error

Then, we simply type "see" to 'see' the errors.

use a free tool from pstools

it is called psexec.  download it and run ti from a command line

www.sysinternals.com

usage: psexec [\\computer[,computer[,..] | @file ][-u user [-p psswd]][-n s][-l][-s|-e][-i][-x][-c [-f|-v]][-d][-w directory][-<priority>][-a n,n,...] cmd [arguments]

so basically you can, after the file is downloaded. type this isn

psexec \\machine_name -u user_name -p password ipconfig /all

see http://www.freevbcode.com/ShowCode.asp?ID=5121 for a vb script wich shows info about a local or remote network adapter and can be easily customized to fit your needs.

i thought mine was better  :)

well , it as , i meant to split the points...i really did installed the pstools...

Oh, Captain ,my Captain ,  please re open the case cause i need to split the points to these two nice gentlemen that took the time to help me out..

thanks everybody.

it is ok.  as long as you got your answer.  

no, i want to split the points..it is a matter of integrity..

Captain, can u please re-open the case ?

I do not object against sharing the points, freya28 deserves them as well as it do. However i must object against his answer being better  ;)

Note that for psexec if you use the name of "\\*" for the computer the command used is automatically ran against all computers in the domain, saving you the trouble of running this on every machine by hand. Actually you could use psexec to run the script i mentioned on all pc's in the domain this way, just make sure it saves the output to some network drive so you can collect it later on.

gentlemen,

the point is that both of you provided really nice answers to my problem and i will be keeping both of these solutions into my knowledge"arsenal"

thanks

I don't like either of your answers, given this question modification:  "can i do anything using vlans or our cisco infrastructure?"

;) <joke>

:)