…… Windows networking issue

[Macgyver]

Is your hosts file clean?
Does it have host name and IP address for your other home network computers in it?

And if you do not know what a hosts file is or where it is located . . . never mind, it is probably clean

Its clean.

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

 

[Macgyver]

That looks a lot better. Saying that it means that you had some network devices that were misbehaving.

I lost you there.

 

[phloydius]

On the problem PC: Is it a new device that has a fresh install from the factory? Or is it a refurb or a new-to-you device?

Do you have any other users on the device? --> Create a new user with administrative rights. Log out of all current users, restart. Log in a new user. See if problem occurs there as well.

 

[raven]

instead of pinging the ip,
ping the host name and see if it resolves correctly to the ip

ping DESKTOP-63N24JR

if it comes back ipv6 use the ipv4 switch
ping DESKTOP-63N24JR -4

 

[raven]

The reason for checking host name resolution on both the problem computer and the target computer is
DNS records are stored in the DNS cache on every machine.
If either have the incorrect ip associated with the other's host name you will have resolution failures.

Usually, the problem resolves itself in short order . . . or else DHCP would be problematic.

 

[Macgyver]

instead of pinging the ip,
ping the host name and see if it resolves correctly to the ip

ping DESKTOP-63N24JR

if it comes back ipv6 use the ipv4 switch
ping DESKTOP-63N24JR -4

C:\Users\SNJ>ping DESKTOP-63N24JR

Pinging DESKTOP-63N24JR [fe80::9364:545d:60d1:128a%11] with 32 bytes of data:
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms

Ping statistics for fe80::9364:545d:60d1:128a%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\SNJ>

 

[raven]

C:\Users\SNJ>ping DESKTOP-63N24JR

Pinging DESKTOP-63N24JR [fe80::9364:545d:60d1:128a%11] with 32 bytes of data:
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms
Reply from fe80::9364:545d:60d1:128a%11: time<1ms

Ping statistics for fe80::9364:545d:60d1:128a%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\SNJ>

that's the correct ipv6 fe80::9364:545d:60d1:128a%11
for itself
is it resolving the Desktop host name correctly?

 

[Macgyver]

that's the correct ipv6 fe80::9364:545d:60d1:128a%11
for itself
is it resolving the Desktop host name correctly?

??

 

[raven]

??

when you pinged the host name, the host name first resolved to the IP address.
But it resolved to the IPv6 IP fe80::9364:545d:60d1:128a%11
that the right IPv6.

If you want it to resolve to IPv4, you have to add the switch to the ping command (-4)
ping DESKTOP-63N24JR -4

It was pinging itself. OK?

NoW ping the other desktop from the laptop the same way

 

[raven]

I have about 5 minutes before I have to run.
However, your network IS routing.
it is not seeing your local workgroup

 

[Macgyver]

when you pinged the host name, the host name first resolved to the IP address.
But it resolved to the IPv6 IP fe80::9364:545d:60d1:128a%11
that the right IPv6.

If you want it to resolve to IPv4, you have to add the switch to the ping command (-4)
ping DESKTOP-63N24JR -4

It was pinging itself. OK?

NoW ping the other desktop from the laptop the same way

C:\Users\SNJ>ping DESKTOP-63N24JR -4

Pinging DESKTOP-63N24JR [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\SNJ>

 

[raven]

Ok. That is the Surface, right.

From there ping Puget-162563 -4
(I think that is the desktop that works)

Puget-162562

 

[Macgyver]

Ok. That is the Surface, right.

From there ping Puget-162563 -4
(I think that is the desktop that works)

C:\Users\SNJ>ping Puget-162563 -4
Ping request could not find host Puget-162563. Please check the name and try again.

 

[Kris Gandillon]

C:\Users\SNJ>ping Puget-162563 -4
Ping request could not find host Puget-162563. Please check the name and try again.

Just catching back up on this thread.

Does the ping above work if you leave off the -4?

That is, does it resolve over IPV6 but not IPV4?

That would definitely be a new clue to understand and possibly narrow down where to look.

ETA: is the name correct? I see 162563 and 162562 mentioned?

 

[raven]

C:\Users\SNJ>ping Puget-162563 -4
Ping request could not find host Puget-162563. Please check the name and try again.

If that is the correct host name, check spelling, then the name is not resolving in DNS.
check the other computers on the network as well.

my first thought for fixing is open a command prompt and enter:
ipconfig /flushdns

google it if you are not familiar with it.

 

[raven]

It's probably because when ping looks up the hostname your DNS returns an ip6 address. Check with whomever is in charge of your DNS server. Just go to network card properties, uncheck the IPV6 address option and restart the machine. default ping to hostname will resolve to ipv4 address

 

[BH]

AP Mode is different from AP Isolation, 2 totally different things - AP Mode turns off DHCP and just runs the wireless radios (you want AP Mode off) - AP Isolation actually isolates each wireless client from other devices on the network (you also want AP Isolation off, so wireless things can see others)

 

[Knoxville's Joker]

I lost you there.

notice how dns, wins, gateway were all the same address. On your wireless computer the addresses were all different. YOu have a malformed wireless configuration or something sending out addresses that should not be.

 

[GeneSD]

Can you show us the DNS settings for the WAN and Lan in the router?

 

[Kris Gandillon]

notice how dns, wins, gateway were all the same address. On your wireless computer the addresses were all different. YOu have a malformed wireless configuration or something sending out addresses that should not be.

I thought I agreed but when I went back through this thread, at least at the IPv4 level Desktop, Puget and Surface all seem to have GW, DHCP and DNS all set to 192.168.1.1 which is what one would typically expect for simple home network without any extraordinary configuration needed.

 

[raven]

you can see your DNS cache with the command ipconfig /displaydns
you can redirect the results to a text file for easier reading (because it will likely be long) with:
ipcnfig /displaydns > C:\PATH\TO\FOLDER\OUTPUT. txt.

the order of name resolution in microsoft tcp/ip is:

1. The client checks to see if the name queried is its own.
2. The client then searches a local Hosts file, a list of IP address and names stored on the local computer.
3. Domain Name System (DNS) servers are queried.
4. If the name is still not resolved, NetBIOS name resolution sequence is used as a backup. This order can be changed by configuring the NetBIOS node type of the client.

What did not occur to me last night is:
When you pinged your local host name without the IPv4 switch, the name resolved to the correct IPv6 IP address.
This indicate that the name resolution is funtioning.
However, when you pinged your local host name with the IPv4 switch (-4), the name did not resolve at all.

If you go through the numbered order above, when the IPv4 switch failed to resolve the IP address, it also failed in the NetBIOS name resolution.
-------------------------------------------------------------------------------------------
Based on all that verbiage, I reviewed the "ipconfig /all" for both DESKTOP-63N24JR and Puget-162562.

Both have
NetBIOS over Tcpip. . . . . . . . : Enabled

Both have
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Both have
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

DESKTOP-63N24JR has
Link-local IPv6 Address . . . . . : fe80::9364:545d:60d1:128a%11(Preferred)
DHCPv6 IAID . . . . . . . . . . . : 127426515
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-A3-6A-AD-98-5F-D3-3A-9D-C5

Puget-162562 does not have IPv6

I would verify on Puget at the command line that ipconfig /all does not return any IPv6 config.
If not, I would review Network Properties for that machine and then review the Network Properties on DESKTOP-63N24JR . . . .

According to one of the forums:
IPv4 and IPv6 are two completely separate protocols, with separate, incompatible packet headers and addressing, and an IPv4-only host cannot directly communicate with an IPv6-only host.

Their solution was:
To dual-stack one or both hosts so that they run both the IPv4 and IPv6 protocols.

Which would seem to be an easy fix by enabling IPv6 on Puget-162562.
Or you could force DESKTOP-63N24JR to only use IPv4
. . . . but it is from the internet so . . . Maybe.

 

[raven]

hmmm . . .
he either fixed it
he stayed up to 3AM working on it and is still asleep

or gave up

 

[Knoxville's Joker]

you can see your DNS cache with the command ipconfig /displaydns
you can redirect the results to a text file for easier reading (because it will likely be long) with:
ipcnfig /displaydns > C:\PATH\TO\FOLDER\OUTPUT. txt.

the order of name resolution in microsoft tcp/ip is:

1. The client checks to see if the name queried is its own.
2. The client then searches a local Hosts file, a list of IP address and names stored on the local computer.
3. Domain Name System (DNS) servers are queried.
4. If the name is still not resolved, NetBIOS name resolution sequence is used as a backup. This order can be changed by configuring the NetBIOS node type of the client.

What did not occur to me last night is:
When you pinged your local host name without the IPv4 switch, the name resolved to the correct IPv6 IP address.
This indicate that the name resolution is funtioning.
However, when you pinged your local host name with the IPv4 switch (-4), the name did not resolve at all.

If you go through the numbered order above, when the IPv4 switch failed to resolve the IP address, it also failed in the NetBIOS name resolution.
-------------------------------------------------------------------------------------------
Based on all that verbiage, I reviewed the "ipconfig /all" for both DESKTOP-63N24JR and Puget-162562.

Both have
NetBIOS over Tcpip. . . . . . . . : Enabled

Both have
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Both have
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

DESKTOP-63N24JR has
Link-local IPv6 Address . . . . . : fe80::9364:545d:60d1:128a%11(Preferred)
DHCPv6 IAID . . . . . . . . . . . : 127426515
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-A3-6A-AD-98-5F-D3-3A-9D-C5

Puget-162562 does not have IPv6

I would verify on Puget at the command line that ipconfig /all does not return any IPv6 config.
If not, I would review Network Properties for that machine and then review the Network Properties on DESKTOP-63N24JR . . . .

According to one of the forums:
IPv4 and IPv6 are two completely separate protocols, with separate, incompatible packet headers and addressing, and an IPv4-only host cannot directly communicate with an IPv6-only host.

Their solution was:
To dual-stack one or both hosts so that they run both the IPv4 and IPv6 protocols.

Which would seem to be an easy fix by enabling IPv6 on Puget-162562.
Or you could force DESKTOP-63N24JR to only use IPv4
. . . . but it is from the internet so . . . Maybe.

Disable all ipv6 on everything ipv4 only internal. Ipv6 is really only used for external network public facing connections.

 

[raven]

Disable all ipv6 on everything ipv4 only internal. Ipv6 is really only used for external network public facing connections.

I wasn't going to muddy the water.
If I was, I would say he has NAT on a private 192 network with 255 host addresses available and less that 255 hosts.
I would not use DHCP for the internal network - just assign each host a unique IPv4 address - except the phone and the firestick. And I would setup DHCP for visitors and the phones - maybe a range of five.

But then I would have to teach the class.

 

[Macgyver]

Ok so getting back to this.
Something is actually wrong with the display on the surface, the screen is twitching and images are ghosting over each other making it un viewable.
So I got that going for me.

I just thought of something and I did a test.
I can normally open a browser on my phone, type in the ip of my pie hole and access the interface. It won't load from my phone.

So I'm leaning to this being an issue with this new router.
I'm going to try calling them in the next day or 2 and let them figure it out.
If that doesn't work I'll put back the old router, if everything works that orbi is getting return.

 

[raven]

Oh good. I thought you had passed out at the keyboard.
LOL

Sorry was no help

 

[lostinaz]

FYI it's ping -4 DESKTOP-XYZ not ping DESKTOP-XYZ -4 to do ipv4

 

[Macgyver]

FYI it's ping -4 DESKTOP-XYZ not ping DESKTOP-XYZ -4 to do ipv4

I cant even see the screen at this point to try it.

 

[raven]

Works both ways apparently.

C:\Users\XXXX>ping DESKTOP-XXXX
Pinging DESKTOP-XXXX [fe80::3723:7b3f:8930:4343%10] with 32 bytes of data:
Reply from fe80::3723:7b3f:8930:4343%10: time<1ms
Reply from fe80::3723:7b3f:8930:4343%10: time<1ms
Reply from fe80::3723:7b3f:8930:4343%10: time<1ms
Reply from fe80::3723:7b3f:8930:4343%10: time<1ms

Ping statistics for fe80::3723:7b3f:8930:4343%10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\XXXX>ping DESKTOP-XXXX -4
Pinging DESKTOP-XXXX [192.168.12.181] with 32 bytes of data:
Reply from 192.168.12.181: bytes=32 time<1ms TTL=128
Reply from 192.168.12.181: bytes=32 time<1ms TTL=128
Reply from 192.168.12.181: bytes=32 time<1ms TTL=128
Reply from 192.168.12.181: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.12.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

[LibertyInNH]

I'll check in your wireless settings if AP isolation is enabled. could be called something like allow intranet as well.

 

[LibertyInNH]

Ok so getting back to this.
Something is actually wrong with the display on the surface, the screen is twitching and images are ghosting over each other making it un viewable.
So I got that going for me.

I just thought of something and I did a test.
I can normally open a browser on my phone, type in the ip of my pie hole and access the interface. It won't load from my phone.

So I'm leaning to this being an issue with this new router.
I'm going to try calling them in the next day or 2 and let them figure it out.
If that doesn't work I'll put back the old router, if everything works that orbi is getting return.

Get rid of the Orbi no matter what.

For soho, use Asus.

TPLink is ok. Ubiquiti or Meraki for complex needs.

 

[Macgyver]

Get rid of the Orbi no matter what.

For soho, use Asus.

TPLink is ok. Ubiquiti or Meraki for complex needs.

Why do you say that about the orbi?

 

[LibertyInNH]

Why do you say that about the orbi?

Netgear has gone downhill over the years. Between over simplification, neutering capabilities, and switching to software as a service model for certain features, to name a few reasons.

another tech pundit, dong knows tech, has written a lot about that. just go to the website and search for orbi. He's already stated it better than I can do here.

 

[Kris Gandillon]

Get rid of the Orbi no matter what.

For soho, use Asus.

TPLink is ok. Ubiquiti or Meraki for complex needs.

My Orbi works just fine. Over 60 WiFi devices (phones, tablets, laptops, TVs, home lighting, locks and security) and 10 wired connections. No issues whatsoever.

 

[aznurse]

So, dumb question and I did not see if this was done. What happens if you go back to the old router? Never had to drill down to the detail in this thread. Learning a lot.

 

[raven]

simple and quick.
just turn off DHCP and assign static IPv4 IPs to your devices.

gets rid of any IPv6 related issue.

 

[Macgyver]

simple and quick.
just turn off DHCP and assign static IPv4 IPs to your devices.

gets rid of any IPv6 related issue.

Could I just turn off the ipv6 on the router?
Really what use is it?

 

[raven]

Could I just turn off the ipv6 on the router?
Really what use is it?

I wouldn't. The router uses IPv6 to talk to the rest of the world (and IPv4).
And most importantly, you can connect to the internet and you know that works
. . . don't mess with what works.
LOL
You already have the list of IPs to use.

your internal network should only need IPv4 (unless there is some specific IPv6 requirement for a particular OS or app)
while you have more hosts on the network than I do . . . you don't have many.
Sounds like Kris Gandillion has a big group AND he has the same router.

(Maaaannnn . . . you need to reach out to Kris and get some assistance - he has 60 nodes and it is working - if he has time - even if you have to wait a few days.)

but you can try it on a couple of machines and see - especially on the one that is being a pain in the butt.
(I think it was 192.168.1.101) Just turn off DHCP on it and configure TCP IP.

I would check your phones to see you can set static IPs. My Motorola can.

The only problem with turning off DHCP is when your ditzy offspring come to the house, like mine,
and wants to connect to your Wi-Fi, it is no longer a matter of giving them the password and router name. now you have to configure their phone.

But you can just set up DHCP for guests . . . maybe 5 . . . unless you party and have a hundred people visit.
That IS what DHCP is for - for laptops that come and go.
I never set hosts (servers in particular) that were physically fixed on DHCP - always static. (Cube farms were DHCP simply because it was easy.)

 

[onetimer]

Going to re-read this thread, might have missed something.

The Orbi mesh system has been solid for everyone I've installed them for so hoping it's a simple setting.

 

[Macgyver]

Going to re-read this thread, might have missed something.

The Orbi mesh system has been solid for everyone I've installed them for so hoping it's a simple setting.

I only have the main orbi right now, no satellites.