PING IN GLOBAL DIRECTORIES for $5

Hi, Warm Greetings! WEBSITE SUBMISSION IN GLOBAL DIRECTORIES Your business page submission in global directories helps for a quick look in search engine pages and helps for a good rating. HERE WE GO WITH MY SERVICES: Quick and Complete service. 200 – 500 Directory submission within 24 Hrs. Submission in high PR directories (3-9 Google PR). 100% genuine and active. Sending report with screen shorts of the submission after completing the work.

by: PreethaN89
Created: —
Category: Directory Submission
Viewed: 118


Serverless/Decentralized Peer to Multi-peer ping system? [on hold]

I have been thinking about an approach through which I can make it possible to have a smartphone app “ping” or alert multiple other smartphones (apps) according to their phone number or userID without having to check in with a central server, the main Idea is to not have a server hosted anywhere (with the exception of the devices/smartphone themselves which can act as servers and clients at the same time.

The obvious challenge doing this is the fact that the source app needs to have some information about the binding (i.e. which username or phone number have which IP address) in order to send that ping.

The research I have done so far suggests that doing this is possible through block-chaining, which also have downsides.

Have anyone worked on or done similar research on something similar to this and kind enough to share their findings?

Update

Since someone put my question on hold, I guess answering in comments will do. Thanks

Ping failure monitor

the network frequently fails and I would like to monitor the output. I tried to makeshift a command like:

ping www.google.fr | while read pong; do echo "$  (date): $  pong"; done 1>/dev/null && 2> ~/ping_err.log 

but the STDERR is still redirected to STDOUT instead ping_err.log

note: I want only STDERR in the file (not 2>&1)

Thanks!

In what situations / with what nodes should a node ping / not ping?

I was recently looking at a network in which the client-machines that accessed a webservice endpoint, but which could not ping the webservice endpoint.

And there are other machines that can ping the webservice endpoint, but which do not utilize it.

However, the other machines do connect to service the client-machines, and of course can ping both.

All machines in question are on a private network, that extends to private and public physical locations.

So, why would some of these machines DROP packets and others ACCEPT them?

Can’t ping the name of the server on Server 2012 R2

Since we do the updates, we found 1 server after reboot we are not be able to ping the NETBIOS (name) of the server from other devices BUT we could ping the IP Address of the server though ?!?!

We also found that when we go to Network (under Network and Sharing Center) and we could NOT find that server name. We could find any servers/desktops.

This network is pretty simple. It a Workgroup (not a DOMAIN) and the DNS on the device pointing to the router/firewall type device.

WINS are also turned on the server and any other devices.

It seem related on the network discovery issue. Any ideas?

Can’t ping the name of the server on Server 2012 R2

Since we do the updates, we found 1 server after reboot we are not be able to ping the NETBIOS (name) of the server from other devices BUT we could ping the IP Address of the server though ?!?!

We also found that when we go to Network (under Network and Sharing Center) and we could NOT find that server name. We could find any servers/desktops.

This network is pretty simple. It a Workgroup (not a DOMAIN) and the DNS on the device pointing to the router/firewall type device.

WINS are also turned on the server and any other devices.

It seem related on the network discovery issue. Any ideas?

I did a IP scan on a network and I see the IP is scannable, but I cannot ping the device

I made a change on a serial-to-ethernet converter and the device is no longer pingable or accessable through the webUI, but when I do a IP scan, NMAP picks it up as:

Nmap scan report for 192.168.0.10 Host is up (0.00069s latency). All 1000 scanned ports on 192.168.0.10 are filtered MAC Address: 00:90:E8:73:1F:16 (Moxa Technologies)

Says the host is up, but I cannot connect whatsover? Is this just stored in the cache? or am I missing something else here?

How can I make sure ping traffic over ipsec is going outside?

I’ve got a VPN tunnel (ipsec / StrongSwan) setup, connected. The other side is apparently able to ping me through the tunnel. However a ping from my side is said to be never received on the other side. The other side (that I cannot control) is thus assuming it’s a configuration issue from my side.

I’m really not sure about this, because I can see the ping packets going out when tcpdumping:

$   ping -c 5 192.168.33.1 PING 192.168.33.1 (192.168.33.1) 56(84) bytes of data. --- 192.168.33.1 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4009ms  (at the same time in another console) $   tcpdump host REMOTE 09:22:07.539582 IP LOCAL > REMOTE: ESP(spi=0xXXXXXX,seq=0x3), length 132 09:22:08.547608 IP LOCAL > REMOTE: ESP(spi=0xXXXXXX,seq=0x4), length 132 (... one packet per ping ...) 

The ESP traffic is obviously my ping. To make sure I’ve disabled all firewalling from my side.

Thus my question: How can I make sure the ping packets are going out and received? What can be the cause and what can I do more to help debug the issue?

As a side note, I’ve got another VPN setup and working, using the exact same configuration.

Fail to ping from single machine to another specific machine

I’m using Google Cloud, there are 2 machines on the cloud which can’t ping each other, A can’t ping B, and B can’t ping A too; all other machines can ping to A&B as usual. But it happens only on Internet IPs, not LAN IPs.*

The difference is this way:

#fails, timeout ping 35.197.x.x #internet ips  #ok as normal ping 10.240.x.x #LAN ips on google cloud 

I have disabled Google Cloud firewall, firewalld service, iptables, ufw; still no luck. Why is it so?

When running ‘netstat -nc’ on the listener server, it keeps showing SYN_RECV and never ESTABLISHED.

#test ssh connection from A to B, #run netstat on B: netstat -nc | grep IP_OF_A