A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Found a fix for sharing



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old July 13th 18, 12:48 AM posted to alt.comp.os.windows-10
KenW[_9_]
external usenet poster
 
Posts: 17
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 20, 2018.


From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?
Ads
  #2  
Old July 13th 18, 12:51 AM posted to alt.comp.os.windows-10
KenW[_9_]
external usenet poster
 
Posts: 17
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 20, 2018.

On Thu, 12 Jul 2018 17:48:27 -0600, KenW wrote:


From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


The errors were Permission And Password.
  #3  
Old July 13th 18, 02:37 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 6,591
Default Found a fix for sharing

KenW wrote:
From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


The one with the IPV6 dependency was HomeGroups.
HomeGroups would not work if IPV6 was disabled.

HomeGroup is deprecated in Windows 10, and is
turned off in 17134. However, the seven or so services
that backed it up, are still running. No idea why.

There is more than one way to disable IPV6, and you
have to be careful about the method used.

I don't know what NetBIOS does in a mixed IPV4/IPV6
situation. IPV6 appears to have some mechanism for
detecting Link Local devices (as otherwise,
enumerating 4 billion link local addresses could
take a while). NetBIOS has something to do with
providing a "neighbors" symbolic list, so you
don't have to use IP numeric addresses to connect.

It helps if the user account you're using, is
common to all the machines. It doesn't mean the
actual user account (SID) is identical on all
the machines. But it does serve the purpose of
authentication for sharing. The SID on each machine
is a very large number, partially randomly assigned,
and is unique.

You can probably set the Permissions on a share
on the serving end, to "deny" others access. Even
if they logged in as "Joe", you could set
the owner to "Henry" and lock Joe out. I can
see a Permissions problem happening if there's
a mixed message in your settings used.

Paul
  #4  
Old July 13th 18, 03:06 AM posted to alt.comp.os.windows-10
KenW[_8_]
external usenet poster
 
Posts: 32
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 20, 2018.

On Thu, 12 Jul 2018 21:37:35 -0400, Paul
wrote:

KenW wrote:
From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


The one with the IPV6 dependency was HomeGroups.
HomeGroups would not work if IPV6 was disabled.

HomeGroup is deprecated in Windows 10, and is
turned off in 17134. However, the seven or so services
that backed it up, are still running. No idea why.

There is more than one way to disable IPV6, and you
have to be careful about the method used.

I don't know what NetBIOS does in a mixed IPV4/IPV6
situation. IPV6 appears to have some mechanism for
detecting Link Local devices (as otherwise,
enumerating 4 billion link local addresses could
take a while). NetBIOS has something to do with
providing a "neighbors" symbolic list, so you
don't have to use IP numeric addresses to connect.

It helps if the user account you're using, is
common to all the machines. It doesn't mean the
actual user account (SID) is identical on all
the machines. But it does serve the purpose of
authentication for sharing. The SID on each machine
is a very large number, partially randomly assigned,
and is unique.

You can probably set the Permissions on a share
on the serving end, to "deny" others access. Even
if they logged in as "Joe", you could set
the owner to "Henry" and lock Joe out. I can
see a Permissions problem happening if there's
a mixed message in your settings used.

Paul


I was correct IPV6 was used for sharing. I have always used a
Workgroup. Will find out tomorrow using the other 'pair'. Will
probably keep using a flash stick anyway, been doing so long it is
built into brain !


KenW
  #5  
Old July 13th 18, 03:32 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 6,591
Default Found a fix for sharing

KenW wrote:
On Thu, 12 Jul 2018 21:37:35 -0400, Paul
wrote:

KenW wrote:
From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?

The one with the IPV6 dependency was HomeGroups.
HomeGroups would not work if IPV6 was disabled.

HomeGroup is deprecated in Windows 10, and is
turned off in 17134. However, the seven or so services
that backed it up, are still running. No idea why.

There is more than one way to disable IPV6, and you
have to be careful about the method used.

I don't know what NetBIOS does in a mixed IPV4/IPV6
situation. IPV6 appears to have some mechanism for
detecting Link Local devices (as otherwise,
enumerating 4 billion link local addresses could
take a while). NetBIOS has something to do with
providing a "neighbors" symbolic list, so you
don't have to use IP numeric addresses to connect.

It helps if the user account you're using, is
common to all the machines. It doesn't mean the
actual user account (SID) is identical on all
the machines. But it does serve the purpose of
authentication for sharing. The SID on each machine
is a very large number, partially randomly assigned,
and is unique.

You can probably set the Permissions on a share
on the serving end, to "deny" others access. Even
if they logged in as "Joe", you could set
the owner to "Henry" and lock Joe out. I can
see a Permissions problem happening if there's
a mixed message in your settings used.

Paul


I was correct IPV6 was used for sharing. I have always used a
Workgroup. Will find out tomorrow using the other 'pair'. Will
probably keep using a flash stick anyway, been doing so long it is
built into brain !


KenW


The machine might have this one built-in.

nbtstat -a bob

where bob is the "name" of the desktop computer.
(I.e. Not a DNS thing, just the desktop name.)

I could find a reference to this as well.

http://www.unixwiz.net/tools/nbtscan.html

http://www.unixwiz.net/tools/nbtscan-1.0.35.exe

nbtscan 192.168.1.0/24

Notice how Kaspersky labels the program. They've labeled
it so you know it's not badware.

https://www.virustotal.com/#/file/c9...4e9e/detection

Here's the result I get.

C:\.... nbtscan-1.0.35__unixwiz_net.exe 192.168.1.0/24

192.168.1.101 WORKGROUP\BOB SHARING
192.168.1.102 WORKGROUP\BLUEWAVE SHARING
*timeout (normal end of scan)

Using ipconfig, perhaps you could try feeding it an IPV6
address. I don't think things use IPV6 here, as my router
doesn't support IPV6 (leaving teredo tunneling perhaps,
if some IPV6 wanted to leave the room). In other words,
I'm not well set up to reproduce what you're seeing.

And that uses the NetBIOS level of nameserving, and isn't
anything to do specifically with DNS. If I were to add
"BOB" to my hosts file, and I was running a web server
on "BLUEWAVE", I would be using DNS if I then typed
http://BLUEWAVE into a browser on the BOB machine.
I think that's about all that a bit of DNS HOST tricks
would buy me. CIFS uses other mechanisms, and for speed
reasons, it's generally better if there's a registration
mechanism for sparsely filled networks, so you don't have
to "scan" the whole damn thing one address at a time.
With the IPV6 extra-large Link Local space, that simply
would not be feasible.

Paul
  #6  
Old July 13th 18, 03:53 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 6,591
Default Found a fix for sharing

KenW wrote:
On Thu, 12 Jul 2018 21:37:35 -0400, Paul
wrote:

KenW wrote:
From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?

The one with the IPV6 dependency was HomeGroups.
HomeGroups would not work if IPV6 was disabled.

HomeGroup is deprecated in Windows 10, and is
turned off in 17134. However, the seven or so services
that backed it up, are still running. No idea why.

There is more than one way to disable IPV6, and you
have to be careful about the method used.

I don't know what NetBIOS does in a mixed IPV4/IPV6
situation. IPV6 appears to have some mechanism for
detecting Link Local devices (as otherwise,
enumerating 4 billion link local addresses could
take a while). NetBIOS has something to do with
providing a "neighbors" symbolic list, so you
don't have to use IP numeric addresses to connect.

It helps if the user account you're using, is
common to all the machines. It doesn't mean the
actual user account (SID) is identical on all
the machines. But it does serve the purpose of
authentication for sharing. The SID on each machine
is a very large number, partially randomly assigned,
and is unique.

You can probably set the Permissions on a share
on the serving end, to "deny" others access. Even
if they logged in as "Joe", you could set
the owner to "Henry" and lock Joe out. I can
see a Permissions problem happening if there's
a mixed message in your settings used.

Paul


I was correct IPV6 was used for sharing. I have always used a
Workgroup. Will find out tomorrow using the other 'pair'. Will
probably keep using a flash stick anyway, been doing so long it is
built into brain !


KenW


The article here, seems to pour cold water on the
notion of NetBIOS.

https://en.wikipedia.org/wiki/NetBIOS_over_TCP%2FIP

Yet the article here, doesn't hint at a superior
replacement.

https://docs.microsoft.com/en-us/pre...=technet.10%29

It's not clear what mechanism replaces it.

There is SSDP, but on Windows 7 that was mainly
used to register things so that the ball and stick
"picture of the network" could be drawn. And the page
here, makes no offhand reference to NetBIOS.

https://en.wikipedia.org/wiki/Simple...overy_Protocol

Paul
  #7  
Old July 14th 18, 12:35 AM posted to alt.comp.os.windows-10
KenW[_9_]
external usenet poster
 
Posts: 17
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 21, 2018.

On Thu, 12 Jul 2018 17:48:27 -0600, KenW wrote:


From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


Doesn't work on the Dell laptop. Last time I buy one of their ****
products. Their forums tell the tale.
  #8  
Old July 15th 18, 05:40 PM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 9,368
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 22, 2018.

On Fri, 13 Jul 2018 17:35:57 -0600, KenW
wrote:

On Thu, 12 Jul 2018 17:48:27 -0600, KenW wrote:


From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


Doesn't work on the Dell laptop. Last time I buy one of their ****
products.


I'm not sure which ones are their **** products, but I agree that it's
best to avoid all **** products. Dell has plenty of decent quality
products, though, so I'd recommend one of those. I have multiple Dell
laptops here and a couple of HP laptops. No issues with any of them.

Their forums tell the tale.


Everyone's forums tell the same tale. The people who post there are the
ones with questions and problems. The people who are out having a good
time aren't posting.

  #9  
Old July 15th 18, 06:46 PM posted to alt.comp.os.windows-10
Ken Blake[_5_]
external usenet poster
 
Posts: 1,686
Default Found a fix for sharing

On Sun, 15 Jul 2018 11:40:58 -0500, Char Jackson
wrote:


Everyone's forums tell the same tale. The people who post there are the
ones with questions and problems. The people who are out having a good
time aren't posting.




Yes. As someone once said, hang around a transmission shop and you'll
think all cars have transmission problems.

  #10  
Old July 15th 18, 08:44 PM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 2,764
Default Found a fix for sharing

On 07/12/2018 04:48 PM, KenW wrote:
Disable IPV6 in Adapter settings


I routinely do this. I have ZERO customer using
IPv6. File sharing work with w10 without it.
  #11  
Old July 16th 18, 12:16 AM posted to alt.comp.os.windows-10
KenW[_9_]
external usenet poster
 
Posts: 17
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 23, 2018.

On Sun, 15 Jul 2018 11:40:58 -0500, Char Jackson
wrote:

On Fri, 13 Jul 2018 17:35:57 -0600, KenW
wrote:

On Thu, 12 Jul 2018 17:48:27 -0600, KenW wrote:


From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?


Doesn't work on the Dell laptop. Last time I buy one of their ****
products.


I'm not sure which ones are their **** products, but I agree that it's
best to avoid all **** products. Dell has plenty of decent quality
products, though, so I'd recommend one of those. I have multiple Dell
laptops here and a couple of HP laptops. No issues with any of them.

Their forums tell the tale.


Everyone's forums tell the same tale. The people who post there are the
ones with questions and problems. The people who are out having a good
time aren't posting.


I even went through GPedit looking for a setting that may block the
network. I never had these problems with HP or Asus. Bad driver
updates that screwed it up. At least I had an image to restore Dell
plays games with their hardware so you can not even get drivers from
the manufactures. I am fed up with this laptop.
  #12  
Old July 16th 18, 02:38 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 6,591
Default Found a fix for sharing

KenW wrote:
On Sun, 15 Jul 2018 11:40:58 -0500, Char Jackson
wrote:

On Fri, 13 Jul 2018 17:35:57 -0600, KenW
wrote:

On Thu, 12 Jul 2018 17:48:27 -0600, KenW wrote:

From the Windows 10 Forums. Disable IPV6 in Adapter settings. Instead
of getting errors when accessing my laptop(wireless) from my
desktop(wireless), it shared without any error.
Tomorrow I will check my other laptop(wireless) & desktop(wired).
I thought I read, years ago, that Win 10 uses IPV6 for sharing ?
Doesn't work on the Dell laptop. Last time I buy one of their ****
products.

I'm not sure which ones are their **** products, but I agree that it's
best to avoid all **** products. Dell has plenty of decent quality
products, though, so I'd recommend one of those. I have multiple Dell
laptops here and a couple of HP laptops. No issues with any of them.

Their forums tell the tale.

Everyone's forums tell the same tale. The people who post there are the
ones with questions and problems. The people who are out having a good
time aren't posting.


I even went through GPedit looking for a setting that may block the
network. I never had these problems with HP or Asus. Bad driver
updates that screwed it up. At least I had an image to restore Dell
plays games with their hardware so you can not even get drivers from
the manufactures. I am fed up with this laptop.


Driver updating should be under manual control.

*Don't* install the Dell auto-updater.

*Don't* enable the Windows hardware driver automatic updater.
There's a setting to disable nuisance Microsoft hardware updates.

Why the reason for this advice ?

Driver updating should be related to symptoms. Does my
Wifi work today ? Good, stop update. Is my Wifi broken ?
OK, go looking for an update (Googling to see if there
is a root cause, and understanding the issues before
proceeding.

Running the computer like "a pot of stew" and
throwing in a few fresh vegetables every day, you're going
to notice occasionally the pot of stew is "off".
Microsoft has caused irrelevant updates to show up
in the update queue for example, and you definitely don't
want those on a machine.

Same goes for the NVidia auto-updater. More opportunities
for mischief than good. Regular updates are required by
gamers, so the latest title has support in the driver.
For other uses of the card, you can easily go years without
needing to touch an update. I worked with a guy in another
group, where I couldn't convince him to disable the
updater, and every time the NVidia driver threw errors,
he was back for help finishing the install. It was
stuff like ShadowPlay, features you could turn off
if manually installing, that kept borking the install.
And you can stay in updater hell, if you keep letting
bad rubbish updates into the machine like that. Who
knows from one day to the next, whether there will be
a working basic video driver ?

Once a machine is stable, stop messing with drivers and
enjoy it. And don't be freaked out, if an INF file in your
new OS has a date of 2003. The INF file itself might have
been stable to changes, way back then. And due to hardware
standards, only stuff not visible at that level is changing.
Never reject a driver just because of a single date you
saw printed somewhere, because that date may be a
"sign of a lack of hygiene" rather than indicating
a functional failure.

In some cases, the OS files might show 17134.165 but some
driver files might show 17134.1 . Which means certain things,
they don't "rev" them for each patch. Again, don't panic - even
though this is a bad practice, to not stamp files in compatible
sets, it doesn't mean the driver is broken. Certain files
are the "engine", and the release numbers on those files
is what counts.

Paul
  #13  
Old July 16th 18, 02:43 AM posted to alt.comp.os.windows-10
...w♂妤比
external usenet poster
 
Posts: 19
Default Found a fix for sharing

"Paul" wrote in message news

It helps if the user account you're using, is
common to all the machines.


1803 and later(i.e. Insider Builds)

Recommended:
Services - enable with Automatic or Automatic Delayed
Function Discovery Resource Publication
Function Discovery Provider Host

Services - Optional(Enable, Automatic) and may be necessary on some devices
SSDP Discovery
UPnP Device Host

Windows Credentials (Control Panel applet = Credential Manager)
- add the Common username/password to each device
Note: From my experience network connectivity and availability across
devices for sharing is slightly faster using an common MSA vs. Local
username/pw in Windows Credentials. Not sure why, possibly some
under-the-hood code.




....w♂妤比
ms mvp windows 2007-2016, insider mvp 2016-2018

  #14  
Old July 16th 18, 02:54 AM posted to alt.comp.os.windows-10
KenW[_9_]
external usenet poster
 
Posts: 17
Default Found a fix for sharing

The author has marked this message not to be archived. This post will be deleted on July 23, 2018.

On Sun, 15 Jul 2018 21:43:10 -0400, ...w♂妤比
wrote:

"Paul" wrote in message news

It helps if the user account you're using, is
common to all the machines.


1803 and later(i.e. Insider Builds)

Recommended:
Services - enable with Automatic or Automatic Delayed
Function Discovery Resource Publication
Function Discovery Provider Host

Services - Optional(Enable, Automatic) and may be necessary on some devices
SSDP Discovery
UPnP Device Host

Windows Credentials (Control Panel applet = Credential Manager)
- add the Common username/password to each device
Note: From my experience network connectivity and availability across
devices for sharing is slightly faster using an common MSA vs. Local
username/pw in Windows Credentials. Not sure why, possibly some
under-the-hood code.




...w♂妤比
ms mvp windows 2007-2016, insider mvp 2016-2018


Another thing I don't like with Dell and to a lessor extent HP, is the
bios updates. I am old enough to remember don't update a bios unless
something is broken and the bios info says what the update does.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 10:19 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 PCbanter.
The comments are property of their posters.