Can't Navigate My LAN Or Ping

[Leonard Chatagnier]

--- On Sat, 12/6/08, Mark Kirkwood <markir at paradise.net.nz> wrote:

> From: Mark Kirkwood <markir at paradise.net.nz>
> Subject: Re: Can't Navigate My LAN Or Ping
> To: "Ubuntu user technical support, not for general discussions" <ubuntu-users at lists.ubuntu.com>
> Date: Saturday, December 6, 2008, 3:53 PM
> Leonard Chatagnier wrote:
> >
> > Karl, you don't read it. The address I used is
> exactly what ATT gave me again and is what I've always
> use to connect to 2Wire's site for administring my
> router setup.  It's not like I haven't done what you
> did a hundred times before. I just can't connect with
> the right url.
> >   
> 
> I was recently helping some of my family with a similar
> problem to this 
> (in their case they did not now the ip of their wireless
> AP, and needed 
> to get to to enable security!).
> 
> What I would do is firstly post the unedited output of
> 'ifconfig' and 
> 'route' to this thread, so everyone knows what your
> workstation 
> networking looks like, then we know a bit more on how to
> help.
> 
> What I world recommend next to to reset your router, and do
> as others 
> have suggested - look online for what the default ip for
> your band and 
> model is (e.g Linksys is typically 192.168.1.1 or
> 192.168.1.254, other 
> bands can be utterly different - for instance Alctel use
> 10.0.0.140 !).
> 
> Once you have some idea what p could or should be, install
> nmap, and 
> scan the entire ip range (e.g To find a Linksys router or
> AP):
> 
> $  nmap -T4 192.168.1.1-254
> 
> You will eventually see something like:
> 
> Interesting ports on 192.168.1.1:
> Not shown: 998 closed ports
> PORT    STATE SERVICE
> 80/tcp  open  http
> 443/tcp open  https
> 
> Which, in this case is my DSL router.
> 
> regards
> 
> Mark
> 
> 
You know, Mark, I've been posting data all day on both threads,
my original post and the second one Karl started and I'm getting
a little weary.  So, I'll not repost what i've posted on the original
but will give you the output of nmap as suggested by someone
else now that it's run its course and also the one you requested
 with a different option.  HTH
lchata at ubuntu:~$ nmap 192.168.1.254

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-06 18:55 CST
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.406 seconds
lchata at ubuntu:~$ nmap -PN 192.168.1.254

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-06 18:55 CST
Stats: 0:01:04 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 3.66% done; ETC: 19:24 (0:28:12 remaining)
Stats: 0:11:26 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 32.20% done; ETC: 19:31 (0:24:03 remaining)
All 1714 scanned ports on 192.168.1.254 are filtered

Nmap done: 1 IP address (1 host up) scanned in 1962.949 seconds
lchata at ubuntu:~$  nmap -T4 192.168.1.1-254

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-06 21:04 CST
Interesting ports on ubuntu (192.168.1.2):
Not shown: 1708 closed ports
PORT     STATE SERVICE
53/tcp   open  domain
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
631/tcp  open  ipp
2049/tcp open  nfs

Nmap done: 254 IP addresses (1 host up) scanned in 3.553 seconds

Leonard Chatagnier
lenc5570 at sbcglobal.net