Re: Can't Navigate My LAN Or Ping
- From: Leonard Chatagnier <lenc5570@xxxxxxxxxxxxx>
- Date: Sat, 6 Dec 2008 21:22:28 -0800 (PST)
--- On Sat, 12/6/08, Mark Kirkwood <markir@xxxxxxxxxxxxxxx> wrote:
From: Mark Kirkwood <markir@xxxxxxxxxxxxxxx>Thank goodness yours is the last unanswered email as of now.
Subject: Re: Can't Navigate My LAN Or Ping
To: "Ubuntu user technical support, not for general discussions" <ubuntu-users@xxxxxxxxxxxxxxxx>
Date: Saturday, December 6, 2008, 10:18 PM
Leonard Chatagnier wrote:
both threads,
You know, Mark, I've been posting data all day on
my original post and the second one Karl started andI'm getting
a little weary. So, I'll not repost what i'veposted on the original
but will give you the output of nmap as suggested bysomeone
else now that it's run its course and also the oneyou requested
with a different option. HTH2008-12-06 18:55 CST
lchata@ubuntu:~$ nmap 192.168.1.254
Starting Nmap 4.53 ( http://insecure.org ) at
Note: Host seems down. If it is really up, butblocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 2.406seconds
lchata@ubuntu:~$ nmap -PN 192.168.1.2542008-12-06 18:55 CST
Starting Nmap 4.53 ( http://insecure.org ) at
Stats: 0:01:04 elapsed; 0 hosts completed (1 up), 1undergoing 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), 1undergoing 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 filtered1962.949 seconds
Nmap done: 1 IP address (1 host up) scanned in
lchata@ubuntu:~$ nmap -T4 192.168.1.1-2542008-12-06 21:04 CST
Starting Nmap 4.53 ( http://insecure.org ) at
Interesting ports on ubuntu (192.168.1.2):3.553 seconds
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
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
the next thing is to move this machine to the router/modem
room an wire it up. The ATT guy didn't do it unless he did
behind my back. The router probably does need to be reset
but I have no idea how the gateway/router IP got changed and
probably wont ever know that it did or what to and I'd like to know
that bit of info. It's been a long hard day on the computer but
I'm now going to direct wire it to the router and start checing
things out using DHCP as NoOp and others suggested. With
all the replies I got on this post it has reinforced how little I
know about networking, modem, routers and wifi cards. And
I did think I was learning a little. I really appreciate all the replies.
And thanks for yours,
BTW there were two people requesting nmap and I may have
attached both to yours.
Leonard Chatagnier
lenc5570@xxxxxxxxxxxxx
--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
- References:
- Re: Can't Navigate My LAN Or Ping
- From: Mark Kirkwood
- Re: Can't Navigate My LAN Or Ping
- Prev by Date: Re: 2 wire DSL
- Next by Date: OP still needs to describe what the post is about
- Previous by thread: Re: Can't Navigate My LAN Or Ping
- Next by thread: Re: Can't Navigate My LAN Or Ping
- Index(es):
Relevant Pages
|
