a wiec ... ja siedze przy 10.0.0.1
tu jes 10002
[polcona@desk1 polcona]$ nmap -sT -vvvv 10.0.0.2
Starting nmap 3.55 (
http://www.insecure.org/nmap/ ) at 2005-07-31 21:40 CEST
Host 10.0.0.2 appears to be down, skipping it.
Note: Host seems down. If it is really up, but blocking our ping probes, try -P0
Nmap run completed -- 1 IP address (0 hosts up) scanned in 10.008 seconds
a tu 10004 na któ¶y moge sie zalogowac
[polcona@desk1 polcona]$ nmap -sT -vvvv 10.0.0.4
Starting nmap 3.55 (
http://www.insecure.org/nmap/ ) at 2005-07-31 21:42 CEST
Host 10.0.0.4 appears to be up ... good.
Initiating Connect() Scan against 10.0.0.4 at 21:42
Adding open port 445/tcp
Adding open port 139/tcp
Adding open port 972/tcp
Adding open port 2049/tcp
Adding open port 988/tcp
Adding open port 6000/tcp
Adding open port 111/tcp
Adding open port 32787/tcp
Adding open port 22/tcp
Adding open port 631/tcp
The Connect() Scan took 0 seconds to scan 1660 ports.
Interesting ports on 10.0.0.4:
(The 1650 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
972/tcp open unknown
988/tcp open unknown
2049/tcp open nfs
6000/tcp open X11
32787/tcp open sometimes-rpc27
Nmap run completed -- 1 IP address (1 host up) scanned in 0.797 seconds
Sam an siebie moge sie zalogowac (czyli 10.0.0.2 na 10.0.0.2) ale juz niegdzie nie moge sie dalej zalogowac, ani do niego