|
Joined: Nov 2004
Posts: 290
Member
|
Member
Joined: Nov 2004
Posts: 290 |
I suppose I can default the switch but this thing has got me wondering if there's a way to determine IP addresses of a particular device on a network You might try this: advanced ip scanner https://www.radmin.com/products/utilities/ipscanner.php
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jun 2005
Posts: 261
Member
|
Member
Joined: Jun 2005
Posts: 261 |
What model switch?
The low end Linksys switches are unmanaged, don't speak IP, and don't have an IP address.
The managed switches generally have a serial port that you can connect to, assuming this it isn't password protected, which would allow you to find the IP address, if one is configured.
|
|
|
|
Joined: Apr 2006
Posts: 2,039
Member
|
OP
Member
Joined: Apr 2006
Posts: 2,039 |
Thanks TDS. That's exactly what I was looking for. :thumb: I'll have to get the model number of the switch tantivity. I'll try to go by today and get it. Edit: I went by today and I was wrong about the brand of the switch. It's a Netgear Prosafe FS116. Which according to my research is a low end product so I don't think there is any kind of IP control in it.
|
|
|
|
Joined: Jan 2008
Posts: 148
Member
|
Member
Joined: Jan 2008
Posts: 148 |
that switch is a dumb one. completely unmanaged.
The IP scanner is nice, but it wont let you find all of the devices on a network, just the ones responding to PING. All the scanner does is ping every IP in a range that you provide. It won't let you find devices configured for an IP outside the range you specify. The best way to find all types of devices using all protocol types (provided they are sending out something) is with a sniffer or packet capture device. The better ones are hardware based and will show all packets. The linix ones for the most part wont catch the error/runt/collision packets that will indicate a problem with the network unless the card it is working with can be set not to filter them at the hardware level prior to passing them up the stack to the application. You may get a flag that it saw an error or runt, but not the content which lets you find the problem.
edit was to change a wrong word.
About me: 8 years of network support 7 years IT field service
Always looking for the next project to be done.
|
|
|
|
Joined: Jan 2008
Posts: 148
Member
|
Member
Joined: Jan 2008
Posts: 148 |
Oh and if you turn on DHCP, make it for a range that doesn't have static addresses. the router may not know they are there if it is rebooted and hasn't yet seen traffic for them if they are off at the time. This can lead to IP conflicts.
About me: 8 years of network support 7 years IT field service
Always looking for the next project to be done.
|
|
|
|
Joined: Apr 2006
Posts: 2,039
Member
|
OP
Member
Joined: Apr 2006
Posts: 2,039 |
Thanks for the info. I've used sniffers on my wireless network when I thought someone was hacking into it but I never thought of one on a wired network.
|
|
|
Forums84
Topics94,284
Posts638,772
Members49,765
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
132
guests, and
349
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|