Unable to ping

Toggle sidebar Toggle sidebar
marnu123

marnu123

Distinguished
Dec 29, 2011
52
0
18,630
Hi

I am running a Win 7 PC connected to a wireless network via a D-Link 2750u router. I am able to connect to the internet and discover other devices on the network, but not ping them. According to Windows troubleshooter, "the DNS server is not responding". We recently replaced our router to the D-Link. I upgraded to Kaspersky Total Internet Security a week ago.

Any help would be greatly appreciated.

Thanks!
 
Sort by date Sort by votes
yeskay

yeskay

Distinguished
Jul 12, 2014
1,258
0
20,460


Hello marnu123,

Use any Open DNS server IP address instead of the default one used by your ISP.
[video="https://www.youtube.com/watch?v=z7Ip3DiHAQ4"][/video]

About Open DNS:
http://en.wikipedia.org/wiki/OpenDNS

I'm currently using this:

OpenDNS Home
208.67.222.222
208.67.220.220

Occasionally, I do change from OpenDNS Home to Norton ConnectSafe:

Norton ConnectSafe
199.85.126.10
199.85.127.10

I also encourage you to try all other Open DNS IP addresses listed here - http://pcsupport.about.com/od/tipstricks/a/free-public-dns-servers.htm

Update:

Kaspersky suggests this solution:

If you cannot connect to the remote desktop of the computer with Kaspersky Internet Security 2015 installed, follow the steps below:

- Open the "Settings" window of Kaspersky Internet Security 2015.

- In the "Settings" window, go to the "Protection Center" section and select "Firewall" in the right frame.
kis15_11601_0113-255055.png

- In the "Firewall settings" window, click the "Configure packet rules" link.
kis15_11601_0213-255057.png

- In the "Packet rules view", select "Remote Desktop" from the list.

- Click "Edit".
kis15_11601_0313-255058.png

- In the "Edit" view, select "Allow" in the "Action" section.

- Click "Save".
kis15_11601_0413-255059.png

- Close the "Packet rules" window.

Source: http://support.kaspersky.com/11601

==================

Nice to know that your problem got solved. Have fun!

Cheers!
 
Upvote 1 Downvote
bicycle_repair_man

bicycle_repair_man

Splendid
Jan 10, 2014
5,752
2
28,960
I assume that you're trying to ping a device on your local network via its host name and not its IP address? If so, you won't be able to as you don't have a local DNS server. Using a DNS server provided by your ISP or a third-party won't help either. These DNS servers will only resolve Internet-facing IP addresses (basically URLs) and not devices on your local network.

In order to ping devices on your local network via the host name, you need to add the devices to the same workgroup.
 
Upvote 0 Downvote
marnu123

marnu123

Distinguished
Dec 29, 2011
52
0
18,630
Thank you @yeskay for your advice. Unfortunately, it didn't work. But my problem, like @bicycle_repair_man states, is that I cannot ping devices on my local network. I have no problem connecting to the internet. I can discover every device present on the network without a problem. The device names IP's are all visible. But I am unable to access these devices, whether through remote desktop or just accessing shared folders.

Using command prompt and the command "ping xxx.xxx.xxx.xxx", the request constantly times out
 
Upvote 0 Downvote
bicycle_repair_man

bicycle_repair_man

Splendid
Jan 10, 2014
5,752
2
28,960
In order to access hosts via Remote Desktop (RDP) the function first needs to be enabled on the target host. Once you've done that, you should be able to RDP using the host's IP address and an administrator account which is local to the host. For example, if the host had an IP address of 192.168.1.10 and an administrator account called 'admin', then you'd use 192.168.1.10/admin for the username, along with the 'admin' account password. An administrator account for the host that you're currently logged on to won't work.

The same principle applies to shared folders except that the account doesn't have to have administrator privileges, just permissions to access the share. From the host that you're currently logged on to, you'd run \\192.168.1.10\sharename.

Without a DNS server on your LAN or a workgroup, you're entirely dependent on using IP addresses.
 
Upvote 0 Downvote
marnu123

marnu123

Distinguished
Dec 29, 2011
52
0
18,630
We have a server on network. Normally, I would RDP into it. But it is inaccessible now.
Using IP addresses. I can ping my PC from other devices on the local network. I thus came to the conclusion that the router is not the problem. I am getting the idea that Kaspersky Internet Security is causing the problem as it is the only change that has been made. Does anyone maybe know of potential problems with it? Google couldn't help me
 
Upvote 0 Downvote
marnu123

marnu123

Distinguished
Dec 29, 2011
52
0
18,630
Problem solved. It turns out that my PC wasn't the problem, but one of the laptops on the network. Kaspersky saw the network as "public" on that PC. Now everything is working again. Thanks!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom