LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   ASUS router not co-operating (https://www.linuxquestions.org/questions/linux-networking-3/asus-router-not-co-operating-885029/)

teboil12 06-07-2011 12:21 PM

ASUS router not co-operating
 
OK
Installed ASUS WL-500gP V2. After a lot of trouble with periodical success getting a HP Deskjet F2420 working and then again not working through this router I thought I had bricked it altogether. Got it back by 30-30-30-method, but now I cannot get through to it, the IP address 192.168.1.1 is not working, somehow. Need to find out if it is recognizing my printer and to see if the connection is protected or open. How the heck can the address all of a sudden not work when the router is working and my Windows (huh...) laptop is connecting OK??? Is there any way of finding out the right address, through the Windows laptop "run" I typed "cmd" and then in the DOS prompt "ipconfig/all" and got a new address = 192.168.2.53, but that did not do any good, either.
Help, anyone???

camorri 06-07-2011 12:38 PM

Have you got the router setup with DHCP? Is the printer configured for DHCP? If yes, then the printer is a moving target. You have two choices, either set the printer up with a static IP address, or go into the router config, find out the MAC address of the printer, and config the router to send out the same IP address for the printer MAC.

A tool you may find helpful is nmap. You can use it to scan a network, for addresses that are in use. So if you don't have too many machines, it can be helpful.

teboil12 06-08-2011 12:56 AM

Now I downloaded nmap and zenmap. Please bear in mind that I am a Ubuntu user but otherwise a bit of a newbie. So could anyone be nice enough as to tell me STEP BY STEP what to do next in order to find the address to this router??? I still cannot get through using the IP address 192.168.1.1 no matter ho hard I try.

onebuck 06-08-2011 07:19 AM

Moved: This thread is more suitable in <Linux-Networking> and has been moved accordingly to help your thread/question get the exposure it deserves.

camorri 06-08-2011 08:45 AM

Once you have nmap and zenmap installed, start up zenmanp, you can start it as a regular user, however it may restrict you as to what you can do with it. So, start it from a command prompt as root user. If your system uses sudo, then 'sudo zenmap' without the quotes should do it.

Near the top of the zenmap window you will see a Target field, and a scan field. There are drop downs. Try a ping scan first. In the target field you need to tell nmap what network, host or router you want. Since its the router you are looking for, and it doesn't seem to respond to the IP address you thought it was, you can wild card the last field, and ping scan will try all addresses in the subnet. You thought it was subnet 192.168.1 so enter 192.168.1.* to get all IP's scanned in the network.

The output will list all devices that respond. See this link for more information on Zenmap -->http://nmap.org/zenmap/

If you do not find the router with this subnet, my best guess next, would be to try 192.168.0.* and see if that turns anything up.

teboil12 06-08-2011 01:23 PM

Thanks for the help sofar. Now I tried "Intense scan", 192.168.1 and 192.168.0 did not give me anything but 192.168.1.1 gave me this:

Starting Nmap 5.51 ( http://nmap.org ) at 2011-06-08 21:11 EEST

NSE: Loaded 57 scripts for scanning.

Initiating Ping Scan at 21:11

Scanning 192.168.1.1 [8 ports]

Completed Ping Scan at 21:11, 2.01s elapsed (1 total hosts)

Nmap scan report for 192.168.1.1 [host down]

Read data files from: /usr/share/nmap

Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn

Nmap done: 1 IP address (0 hosts up) scanned in 2.81 seconds

Raw packets sent: 16 (640B) | Rcvd: 0 (0B)

Does this tell you anything important? What does "try -Pn" mean?

camorri 06-08-2011 01:40 PM

Quote:

Does this tell you anything important? What does "try -Pn" mean?
There is a 'Command' field below the Target line. In there you will see some things like this
Quote:

nmap -T4 -A -v 192.168.1.1
The letters after nmap are the options. You can manually edit the options. They are suggesting you add the option -Pn. From the man page here is what -Pn does:

Quote:

-Pn (No ping) .
This option skips the Nmap discovery stage altogether. Normally,
Nmap uses this stage to determine active machines for heavier
scanning. By default, Nmap only performs heavy probing such as port
scans, version detection, or OS detection against hosts that are
found to be up. Disabling host discovery with -Pn causes Nmap to
attempt the requested scanning functions against every target IP
address specified. So if a class B target address space (/16) is
specified on the command line, all 65,536 IP addresses are scanned.
Proper host discovery is skipped as with the list scan, but instead
of stopping and printing the target list, Nmap continues to perform
requested functions as if each target IP is active. To skip ping
scan and port scan, while still allowing NSE to run, use the two
options -Pn -sn together.

For machines on a local ethernet network, ARP scanning will still
be performed (unless --send-ip is specified) because Nmap needs MAC
addresses to further scan target hosts. In previous versions of
Nmap, -Pn was -P0. and -PN..

teboil12 06-09-2011 05:12 AM

The command field was like this: nmap -T4 -A -v -PE -PS22,25,80 -PA21,23,80,3389 192.168.1.1

I added -Pn and got this:Starting Nmap 5.51 ( http://nmap.org ) at 2011-06-09 13:08 EEST
NSE: Loaded 57 scripts for scanning.
Failed to resolve given hostname/IP: 192.168.1.1-Pn. Note that you can't use '/mask' AND '1-4,7,100-' style IP ranges
Read data files from: /usr/share/nmap
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.93 seconds
Raw packets sent: 0 (0B) | Rcvd: 0 (0B)

Not very encouraging, eh?

I have understood that the host is "down" and there is a need to find out how to get it back "up". Am I totally out in the woods???

camorri 06-09-2011 08:56 AM

It looks to me as the command line is not correct. Please try this;

Quote:

nmap -T4 -F Pn 192.168.1.1
I tried this on my router, it produced this:

Quote:

Starting Nmap 5.51 ( http://nmap.org ) at 2011-06-09 09:52 EDT
Nmap scan report for Pn (67.215.65.132)
Host is up (0.10s latency).
rDNS record for 67.215.65.132: hit-nxdomain.opendns.com
Not shown: 91 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
8000/tcp open http-alt
8008/tcp open http
8009/tcp open ajp13
8080/tcp open http-proxy
8081/tcp open blackice-icecap
8443/tcp open https-alt
8888/tcp open sun-answerbook

Nmap scan report for 192.168.1.1
Host is up (0.0080s latency).
Not shown: 99 closed ports
PORT STATE SERVICE
443/tcp open https

Nmap done: 2 IP addresses (2 hosts up) scanned in 2.90 seconds
If you know the IP address is correct, and you do not get a response, there is something wrong with the router. It may be configuration, I don't know for sure. I would want to take a look at the config, and go from there.

teboil12 06-09-2011 10:57 AM

This is what I got:

Starting Nmap 5.51 ( http://nmap.org ) at 2011-06-09 18:55 EEST
Nmap scan report for Pn (80.68.93.100)
Host is up (0.11s latency).
rDNS record for 80.68.93.100: tedside.pitcairn.net.pn
Not shown: 92 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp filtered smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
587/tcp open submission
995/tcp open pop3s

Nmap done: 2 IP addresses (1 host up) scanned in 3.47 seconds

What does it tell you???

camorri 06-09-2011 01:25 PM

It worked.
Quote:

80.68.93.100: tedside.pitcairn.net.pn
Your ISP I suspect. I can ping that address, and do a traceroute to it. So, you got to your router, and onto your ISP. If you click on the Topology tab, it should show your router, and the your ISP.

teboil12 06-10-2011 12:52 AM

OK, I went to Topology and then I asked myself what now? I can see the picture, but what to do with it? As I said, I am more of a newbie and I have to learn this the hard way, especially when my language is finnish...

camorri 06-10-2011 09:08 AM

What the successful test means, is you can get to the router. Not at all sure why it doesn't answer a ping. I know some routers can be configured not to answer a ping. The Topology picture is just that, a picture showing how far the test went. So, back to the original problem, you have a printer on the network you can not get to.

Do you know the IP address of the printer? Have you got it in your /etc/hosts file? If not, can you add it, and try a ping to it?

teboil12 06-14-2011 12:07 AM

Cannot find any IP address on the printer. Not in /etc/hosts either... Back to square one.

camorri 06-14-2011 08:44 AM

How does the printer get its IP address? Have you configured it? Does the printer do a DHCP request, and the IP is assigned by the DHCP server? Is the server in your router?

Do you know how to connect to the router and look at its configuration? Most routers I have looked at will show you what device has what IP address.

Using DHCP for a network printer is not a good idea, since the address can be different from time to time. It becomes a moving target. Once again, in the router config you can probably set it up so the printer always gets the same IP address. You simply reserve IP address for a specific MAC address. Most routers support a function like that.


All times are GMT -5. The time now is 06:11 AM.