Can't Navigate My LAN Or Ping

[Mark Kirkwood]

Leonard Chatagnier wrote:
>
> 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
>
>   
Not surprising - good on you answering all those emails :-). Maybe take 
a rest and read the the remainder of this tomorrow!

LOL, I'm pretty sure I suggested both nmap runs! The output is very 
interesting. The first scan does not find any host at 192.168.1.254, and 
as for the second - the only address to answer is 192.168.1.2. This 
strongly suggests that the ip of your router is *not* 192.168.1.254 (i.e 
it has been changed... possibly at the recommendation of the ATT guy).

Reading no0p's post, I concur with his recommendation (i.e move the 
2wire, plug in ethernet and retest, and factory reset if still no 
connection)

regards

Mark