M
Mike Hyndman
Is there a utility that can be run on an NT4 server which will display
the IP addresses of all the connected PC's.(WXP)
TIA
Mike H
the IP addresses of all the connected PC's.(WXP)
TIA
Mike H
C
CJT
Mike said:
"Connected" in what sense?
Accessible?
In the arp table?
Currently doing accesses?
....
M
Mike Hyndman
40+ PC's , WAP's, gateways etc., all access able from the server. The IP
addresses are fixed not dynamic. Since replacing 20 PC's, we have been
getting a message on some that their address already exists on the
network. (IP addresses merely replicated from the PC's which were
replaced, which never exhibited this problem)The IP address is then
changed and all is the well for a few days then the message appears on
other PC's. I know that the one way would be to go around all the PC's
etc., and do an IP config for the info but it would be quicker if
something could be run centrally. I think that the problem is down to
people using laptops on the wireless part of the network.
Many thanks
MH
C
CJT
In that case, you need to look at the range of addresses the DHCPMike said:
service associated with the wireless is handing out.
K
Kurt
nbtstat -A <ip address> will list the netbios name of the computer with that
IP address (obvioiusly won't work from the computer reporting the IP address
conflict).
nbtstat -a <computername> will do the reverse.
For either, the computer must be in broadcast range and NetBios over TCP/IP
enabled, or registered in WINS.
Other than that, you can ping, do "arp -a" and you'll get the mac address,
but really doesn't help you to identify the location of the machine. There
are utilities like LanGuard LanNetScan that'll report al kinds of stuff.
Beware, it's likely to set off alarms if you have network security in place.
I'd take the opportunity to visit each machine, gather information and put
it in a spreadsheet for future reference. Then INSIST that your net admin
staff input changes whenever they move a computer, change a NIC, change an
IP address, etc. Also, with 40 computers, maintaining a static network is
getting labor intensive enough to switch to DHCP. Let DHCP register each
lease in DNS, and you'll never need to look any farther than you DNS snap-in
to identify which computer has which IP address.
....kurt
IP address (obvioiusly won't work from the computer reporting the IP address
conflict).
nbtstat -a <computername> will do the reverse.
For either, the computer must be in broadcast range and NetBios over TCP/IP
enabled, or registered in WINS.
Other than that, you can ping, do "arp -a" and you'll get the mac address,
but really doesn't help you to identify the location of the machine. There
are utilities like LanGuard LanNetScan that'll report al kinds of stuff.
Beware, it's likely to set off alarms if you have network security in place.
I'd take the opportunity to visit each machine, gather information and put
it in a spreadsheet for future reference. Then INSIST that your net admin
staff input changes whenever they move a computer, change a NIC, change an
IP address, etc. Also, with 40 computers, maintaining a static network is
getting labor intensive enough to switch to DHCP. Let DHCP register each
lease in DNS, and you'll never need to look any farther than you DNS snap-in
to identify which computer has which IP address.
....kurt
C
CJT
Sorry, I realize now I was off point, because you said you're usingCJT said:
static addresses. That's why DHCP was invented. After a point, with
a dynamic network, the management of static addresses is unwieldy.
M
Mike Hyndman
Kurt,
Many thanks, I don't think that DHCP is an option as we need to be
found, by our "superiors" at a certain address and not that one that
could change by a few points each time, for file transfer etc, hence the
static addresses. When the network was first installed it only had 10
PC's attached to the router, but with the advent of wireless it has
tended to expand somewhat. I thought that the only way to sort it would
be to go around them all....;-(
Again many thanks
Mike H
M
Mike Hyndman
Tell me about it!
Again many thanks
Mike H
J
Jan
Click Start then Help and Support to open XP's Help and Support
Center.
Choose "Networking and the Web."
Click "Fixing networking or Web problems" on the left,
Then : under Pick A Task on the right choose:
"Diagnose network configuration and run automated networking tests".
Choose "Scan your system."
OR Check off appropriate boxes in "Set scanning options" first then
click Scan Your System.
Jan
C
CJT
Jan said:
Is that also available under NT4 as requested?
J
Jan
Sorry I dont do requests!!!
K
Kurt
How 'bout impressions?
Jan said: