| 1 |
On Sunday 12 Feb 2017 01:07:09 thelma@×××××××××××.com wrote: |
| 2 |
> On 02/12/2017 01:01 AM, thelma@×××××××××××.com wrote: |
| 3 |
> > My local network is 10.0.0.1 - |
| 4 |
> > |
| 5 |
> > I have an external device that is pre-set from factory to 192.168.1.100 |
| 6 |
> > and I need to access to it via browser to change its network setting. So |
| 7 |
> > I do: |
| 8 |
> > ifconfig net0:1 192.168.1.1 up |
| 9 |
> > |
| 10 |
> > nmap -sn 192.168.1.1/24 |
| 11 |
> > |
| 12 |
> > Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST |
| 13 |
> > Nmap scan report for 192.168.1.100 |
| 14 |
> > Host is up (0.00015s latency). |
| 15 |
> > MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications) |
| 16 |
> > Nmap scan report for 192.168.1.1 |
| 17 |
> > Host is up. |
| 18 |
> > Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds |
| 19 |
> > |
| 20 |
> > The device is showing up but I can not ping it, 100% packet loss. |
| 21 |
> |
| 22 |
> ifconfig is showing: |
| 23 |
> |
| 24 |
> net0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 |
| 25 |
> inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255 |
| 26 |
> ether 00:1b:21:b8:27:b6 txqueuelen 1000 (Ethernet) |
| 27 |
> device interrupt 16 memory 0xfddc0000-fdde0000 |
| 28 |
> |
| 29 |
> -- |
| 30 |
> Thelma |
| 31 |
|
| 32 |
Are you sure the device is configured to respond to pings? |
| 33 |
|
| 34 |
Are your routes on the PC configured correctly, if you are using a secondary |
| 35 |
interface on the same NIC? |
| 36 |
|
| 37 |
Does nmap -A -T4 -Pn -vvv 192.168.1.100 show any services running to which you |
| 38 |
can connect? |
| 39 |
|
| 40 |
-- |
| 41 |
Regards, |
| 42 |
Mick |
Archives