1. If you have access to the DHCP server, and depending on
what you are running as the DHCP server OS, you should be
able to lookup by mac address, and see who the lease is
going to.
2. For the ip address resolution into name you could open
a command prompt, and type "nslookup" and then type in the
IP address. That is not always on point, but its a start.
Also, like above if you have access to the DHCP server,
you can also just look up on there by IP address.
If you are having problems logging onto the network, and
they are between 2k boxes, you may want to look into
changing their SID. This is a Security ID in the NTFS file
system. I believe it does not pertain to the NT boxes. I
may be in correct though. You can get a utility from
Norton Ghost that will change the SID for you, to a unique
one. I have had problems with trust relationship failures
upon login. This may be a fix for you, unless the error
msg's are on point with the IP conflict.
FYI, Mac addresses are unique, so there cant be two of the
same ones. TO see if a network card is in working order,
ping it. 127.0.0.1 is its loopback address, if you can
ping that, the card is 99% in working order. I hope I have
helped you.
>-----Original Message-----
>Dumb questions, I know. I just can't remember some
things:
>
>1. If I know the MAC of some machine out there on the
network that
>supposedly is having a conflict with anther machine on a
win2k3 network, how
>can I identify the other client machine's name? Clients
are 95, 98, NT, and
>2k.
>
>2. Same kinda question again but: If I know the IP
ADDRESS of a machine
>that supposedly is having a conflict with another machine
on a win2k3
>network, how can I determine the client machine's name?
>
>(I've got some conflicting info, some error messages at
one machine that
>indicate that it is having either IP address conflicts
with another machine
>or that the MAC is identical to another machine. Not
sure which messages to
>believe so I want to nail down what machine exactly out
there that its
>complaining about. Traded NICS and the errors went away
but I'm wondering
>if that NIC is really bad, second NIC in a week for that
machine.)
>
>Thanks in advance for any help. Remove "nospam" if
replying directly.
>
>Dave Niemeyer
>
>
>.
>
|