Entering that ip address in a browser brings up the username/login of that router acting as bridge. I can eyeball each one and say, aha, the 192.168.13.101 is my missing wireless bridge. So what this tells me is that those IP addresses listed were the only ones responding to pings. On the IP Lookup page, you’ll get a quick overview of the following: The IP address detected and information about your IP address: ISP: Internet Service Provider. Nmap done: 61 IP addresses (5 hosts up) scanned in 1.66 seconds Nmap command produces output: Starting Nmap 6.01 ( ) at 23:12 EDT The 80-140 token at the end of the ip address means scan for ip addresses 192.168.13.80 through 192.168.13.140. The -sP flag tells nmap to (not search ports) after a host is discovered. Package 2:86_64 already installed and latest version Install nmap on the linux bin]# yum install nmap This will greatly shrink your search space. nmap will scan all your IP addresses for responding ones. If you have Linux, nmap will solve your problem. How to find the lost IP address of a wireless bridge: Make sure it is configured correctly and restart it. If you are still not working, try configuring your client manually and seeing if you can access the router and everything works, if so your DHCP server may be flaked out. Run "ipconfig /release" to let go of the old DHCP lease, then run "ipconfig /all" to make sure you see an unconfigured interface, finally run "ipconfig /renew" to get a new address, hopefully you will now see usable addresses. If you've forgotten your router's password. Otherwise, you must factory reset your router to set a new password. If the server doesn't answer up then you probably have old info in there. If you can't log in to your router because you forgot the password, consult the router's manual, look for a sticker on the router itself, and check for the default password used by your router. If any of those work you probably have multiple devices in router mode on your network, find and remove the rogue. If it is DHCP enabled the "DHCP Server." field will identify the server it got the address from, try pinging, and connecting to that address via HTTP and HTTPS. If not, then go into your TCP/IP properties and enable DHCP or manually configure the client IP settings. Run "ipconfig /all" and check to see if it says "DHCP Enabled.Yes". The question to answer would be where did the current default gateway address from. Funny prerequisite question, are you sure you're on the right wireless network? Sorry, but experience has taught me to always ask that first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |