Ask Question Forum:
Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by Salonge
at 2024-07-16 08:02:34
ModifyPoint:500 Replies:20 POST_ID:828592USER_ID:11430
Topic:
Network Management;;Network Routers
I really need help. I have a site that uses DHCP for all its wireless and wired devices. The router is a Cisco 2901 and hands out IP's dynamically with no problems until this past week. It appears that whenever a computer is turned off and back on, the IP address is changed to a public IP - 192.168.0.x. After some investigation, I realized that it is a device somewhere, we are unable to locate it, that is handing out public IP's. This is forcing me to put static IP's on our computers. I have the mac address and was able to find the brand name of the device, but unable to find the device itself. I put the public ip gateway in one of the computers and was able to pull up a login page, but all the default username/password combination does not work.
Is there a way
1. to find the location of the device;
or
2. Block it, so that our network won't pick up the addresses.
Thanks so much
Is there a way
1. to find the location of the device;
or
2. Block it, so that our network won't pick up the addresses.
Thanks so much
Author: Salonge replied at 2024-07-18 13:05:20
Thank you again.
Expert: skullnobrains replied at 2024-07-18 13:02:58
removing it altogether was definitely another solution ;)
looks like you earned a home router for personal use
best regards
looks like you earned a home router for personal use
best regards
Author: Salonge replied at 2024-07-18 12:36:14
I was able to find the device my trying to log into the ip address given and the machine that was connected to the port, stopped working. This led me to look at her connection and the little hub/switch that she was connected to. Unplugged that device and everything is now working fine.
Expert: skullnobrains replied at 2024-07-18 09:28:39
you'll have to do a little googling or dig up the documentation.
many switches will not ask for a password when you reboot them with a serial cable plugged, others will have features to let anyone authenticate from any port by pressing a button. I do not know the model so i cannot tell
many switches will not ask for a password when you reboot them with a serial cable plugged, others will have features to let anyone authenticate from any port by pressing a button. I do not know the model so i cannot tell
Author: Salonge replied at 2024-07-18 09:14:21
I do know the model, how would I do that?
Thanks so much.
Thanks so much.
Accepted Solution
Expert: skullnobrains replied at 2024-07-18 09:11:43
500 points EXCELLENT
if you know the model of the switch, you should be able to log into it even if you do not know the password and deactivate the dhcp server (or set it up properly). it is a managed switch if it features dhcp.
if this is a pain and if no non-static machines is plugged onto it, you can also go the dirty way and setup ACLS to block dhcp ports on the neighbouring switch.
as a side note, most likely this means your primary dhcp is a little overloaded compared to before, or you made changes to the network such a sremoving an ACL or making a VLAN available where it did not use to be
if this is a pain and if no non-static machines is plugged onto it, you can also go the dirty way and setup ACLS to block dhcp ports on the neighbouring switch.
as a side note, most likely this means your primary dhcp is a little overloaded compared to before, or you made changes to the network such a sremoving an ACL or making a VLAN available where it did not use to be
Author: Salonge replied at 2024-07-18 08:53:55
thanks - the interesting point is that my private dhcp server is 10.100.x.x and the mystery dhcp device is 192.168.0.1
I really don't know how to fix it. It appears to be a switch, so I may have to redo the switch.
I really don't know how to fix it. It appears to be a switch, so I may have to redo the switch.
Expert: skullnobrains replied at 2024-07-18 08:30:51
Don't care about points here.
as a general rule, you can look at The switches arp tables. They specify on which port is each arp address they know about so you can easily find any device.
In many cases you can do this through snmp without even logging on the switch.
@Salonge : In your case, either the dhcp ports were blocked previously, or a race condition between dhcp servers changed winner
as a general rule, you can look at The switches arp tables. They specify on which port is each arp address they know about so you can easily find any device.
In many cases you can do this through snmp without even logging on the switch.
@Salonge : In your case, either the dhcp ports were blocked previously, or a race condition between dhcp servers changed winner
Author: Salonge replied at 2024-07-17 10:34:20
Good advice was given, but the advice was not helpful to me. I clearly stated that I was unable to find the physical device and was given advice on how to reset a password on the device. I had the IP address and the model of the device. I justed needed to know how to find it and block it, if possible. I was even told to look through the thread to see what I could find. I was able to find the device, by going into by working with a networking support person, who logged into my router and found the device and which port it was using on my switch.
thanks
thanks
Expert: fmarshall replied at 2024-07-17 10:23:15
It seems to me that good advice was given regarding how to find a rogue IP device.
And, a rogue IP device was found - but not clear how.
And, a rogue IP device was found - but not clear how.
Author: Salonge replied at 2024-07-17 05:19:07
I was able to find my own solution
Author: Salonge replied at 2024-07-17 05:18:17
I've requested that this question be closed as follows:
Accepted answer: 0 points for Salonge's comment #a39332997
for the following reason:
I was able to find my own solution
Accepted answer: 0 points for Salonge's comment #a39332997
for the following reason:
I was able to find my own solution
Author: Salonge replied at 2024-07-17 05:17:41
I found it. It is an additional switch on my network that is not managed, but for some reason just started handing out IP's. I will have to get into the switch and see if I can turn it off.
Thanks for all of your help.
Thanks for all of your help.
Expert: fmarshall replied at 2024-07-16 15:30:58
I was able to connect to the device,
So, either you have it's network name or its IP address.
From the name you can get the address using:
ping [name]
From the ip address you can get the name:
nbtstat -a [ipaddress]
Were you using telnet or http with a browser to get the login?
Knowing it's Leviton is a step in the right direction.
I don't see where they manufacture anything like a device that would have DHCP service however.....
Author: Salonge replied at 2024-07-16 12:21:33
No, I learned nothing from the IP address. I was able to connect to the device, but was unable to login, it kept asking me for a username and password. There was nothing on the screen. The only manufacturing info was a Leviton equipment. We don't have any equipment like that at our site.
Expert: duncanb7 replied at 2024-07-16 12:20:26
do the reset for 30 second and let login as blank and type password to "admin" on IP of 192.168.1.1
that will get into the login page and modify any setting you want after
just go ahead to do , and you get the final
Hope it will help
Duncan
that will get into the login page and modify any setting you want after
just go ahead to do , and you get the final
Hope it will help
Duncan
Expert: fmarshall replied at 2024-07-16 12:06:43
Apparently you do have its IP address as you were able to reach the login screen.
Did you learn anything from that?
What is the IP address?
Was there any sort of model or manufacturer info on the login screen?
Have you tried searching EE using "rogue IP" as I suggested.
Note the spelling, it's rogue not rouge.
Did you learn anything from that?
What is the IP address?
Was there any sort of model or manufacturer info on the login screen?
Have you tried searching EE using "rogue IP" as I suggested.
Note the spelling, it's rogue not rouge.
Author: Salonge replied at 2024-07-16 11:59:43
My problem is that I cannot find the device on my network. I am trying to find the device that is giving out the 192.168.x.x. ip addresses.
Expert: duncanb7 replied at 2024-07-16 11:55:28
There is reset button at the back of the router device, please
press it for 30 seconds, and then try again 192.168.1.1
It should be worked for CISCO device
IF not working, please restart the whole computer and so the same to reset
the button for 30 second and try 192.168.1.1 on browser again
It should work
Duncan
press it for 30 seconds, and then try again 192.168.1.1
It should be worked for CISCO device
IF not working, please restart the whole computer and so the same to reset
the button for 30 second and try 192.168.1.1 on browser again
It should work
Duncan
Expert: fmarshall replied at 2024-07-16 08:09:57
192.168.0.x is a private range ... just for reference.
Although, it may well be used as a subnet for what some facilities would call a "public" network.
It's private because it is in a range that's not propagated over the internet.
Otherwise, it appears you have the age-old problem of "how do I find this red rogue device on my network?" There are lots of threads here on EE that deal with that issue.
Although, it may well be used as a subnet for what some facilities would call a "public" network.
It's private because it is in a range that's not propagated over the internet.
Otherwise, it appears you have the age-old problem of "how do I find this red rogue device on my network?" There are lots of threads here on EE that deal with that issue.
