Win 10 & XP shares

Well everything all worked well until last update to Windows 10 on my
one pc running it. It now no longer seems to want to see the XP pc on my
network that it always did before, everything else it sees no problems.
And the XP pc in question is seen by all the other pc's in the house.

I wouldn't put it past MS to start "locking out" things in Windows 10 so
wondering if killing connecting to older OS's in one of them?

Anyone?

pjp wrote:

Well everything all worked well until last update to Windows 10 on my
one pc running it. It now no longer seems to want to see the XP pc on my
network that it always did before, everything else it sees no problems.
And the XP pc in question is seen by all the other pc's in the house.

I wouldn't put it past MS to start "locking out" things in Windows 10 so
wondering if killing connecting to older OS's in one of them?

Anyone?

Mine works here. Tested this morning.

*******

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32 get-smbconnection

ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
BOB ramdisk WAFFLES\User Name WAFFLES\User Name 1.5 2

PS C:\WINDOWS\system32

*******

Unfortunately, that utility only shows what happened if a
connection is successful.

And you'll notice that the Dialect is not in
the list of numbers here. What does that
mean, exactly ? AFAIK, WinXP is SMB1, and relies
on stuff like NetBIOS for nameserving.

https://blogs.technet.microsoft.com/...are-you-using/

*******

OK, found another command to try.

https://support.microsoft.com/en-us/...ws-server-2012

PS C:\WINDOWS\system32 get-smbserverconfiguration

AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 64
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 10
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : False
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : True
EnableSecuritySignature : False
EnableSMB1Protocol : True -------
EnableSMB2Protocol : True -------
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True

It's funny there is no flag for SMB3.

And my EncryptData is set to false. I thought the
options were either 40 bit or 128 bit AES. I don't think
I've been modifying this stuff.

*******

In Win10 Creator, type "Control" in the Cortana search hole.
When the Control Panel shows up, look for Troubleshooting.
Then type "Shared" into the search in the upper right,
to locate the "Shared Folders" troubleshooter. Maybe
it knows what's wrong.

Paul

On 03 May 2017, pjp wrote in
alt.comp.os.windows-10:

Well everything all worked well until last update to Windows 10 on
my one pc running it. It now no longer seems to want to see the XP
pc on my network that it always did before, everything else it
sees no problems. And the XP pc in question is seen by all the
other pc's in the house.

I wouldn't put it past MS to start "locking out" things in Windows
10 so wondering if killing connecting to older OS's in one of
them?

All I can say is that my Windows XP, Vista, 7, and 10 computers see
each other across the network as well and consistently as they always
did.

On 5/3/2017 1:36 PM, Wolf K wrote:
On 2017-05-03 12:02, pjp wrote:


Well everything all worked well until last update to Windows 10 on my
one pc running it. It now no longer seems to want to see the XP pc on my
network that it always did before, everything else it sees no problems.
And the XP pc in question is seen by all the other pc's in the house.

I wouldn't put it past MS to start "locking out" things in Windows 10 so
wondering if killing connecting to older OS's in one of them?

Anyone?

Try disconnecting the XP machine, then reconnecting it to the network.
I'd even a do reboot between disconnect/reconnect.

Good luck,

I've had connection issues that I fixed by:
shutdown all PC's
reboot router
restart all PC's
Wait
And it eventually fixed itself.
There are actual network commands to do all that,
but I can't remember them when I need them, and
whatever I typed didn't fix the problem.

I can't vouch for which way MS has set the swtich
in any version of win10, but there's an option in
system properties/remote that turns on remote desktop.
There's a checkbox that restricts whether XP's
lower security can
connect in that mode. Don't know if that does
anything when not in remote access.

There's a registry setting regarding
network connection to less-safe systems.

To share files with PDA and linux, had to edit the registry
to relax network security.

Open Registry Editor, navigate to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Lsa\

Create LMCompatibilityLevel (DWord) and set the value to 1

I haven't tried to do this in win10 yet. Works well in 7.



Firewall can cause the problem.
Depending on your settings, the new system may restrict
access to your XP system.

One issue with in-place updates is that you need to set
a new user name to continue.
I've had to set the new user,
Install
Boot
logout
login to old user
delete new user.

Depending on your settings, a new in-place
install will still set a new computer name.
If you miss that and don't reset it, or
fail to set it to the EXACT name of the previous
version, this can bork your network.

On Wed, 03 May 2017 14:39:07 -0400, Nil wrote:

All I can say is that my Windows XP, Vista, 7, and 10 computers see
each other across the network as well and consistently as they always
did.

Ha! Pity then that so many people have problems with this. As a
minimum to get things going I have to ensure all machines have an
account running with the same user name and password, and fix the IP
addresses rather than using DHCP and relying on machine names.

Check after reboot if networking is OK, if not then:
enable NetBIOS over TCP/IP in the properties of IPv4, under the WINS
tab, within the properties of your network interface card.
type "services.msc"
into the search box and hit enter,
confirm that the following services are started, consider setting
the startup type to automatic:

Computer Browser
Function Discovery Provider Host
Function Discovery Resource Publication
Network Connections
Network List Service
Network Location Awareness
Network Store Interface Service
Server
SSDP Discovery
TCP/IP NetBIOS Helper
Workstation

After changes reboot everything including router, cross fingers!

mechanic wrote:
On Wed, 03 May 2017 14:39:07 -0400, Nil wrote:

All I can say is that my Windows XP, Vista, 7, and 10 computers see
each other across the network as well and consistently as they always
did.

Ha! Pity then that so many people have problems with this. As a
minimum to get things going I have to ensure all machines have an
account running with the same user name and password, and fix the IP
addresses rather than using DHCP and relying on machine names.

Check after reboot if networking is OK, if not then:
enable NetBIOS over TCP/IP in the properties of IPv4, under the WINS
tab, within the properties of your network interface card.
type "services.msc"
into the search box and hit enter,
confirm that the following services are started, consider setting
the startup type to automatic:

Computer Browser
Function Discovery Provider Host
Function Discovery Resource Publication
Network Connections
Network List Service
Network Location Awareness
Network Store Interface Service
Server
SSDP Discovery
TCP/IP NetBIOS Helper
Workstation

After changes reboot everything including router, cross fingers!

On the Insider Edition, there were occasional problems with
SMB. Some editions had disabled some of the protocol options.
I whined loudly into a Insider Hub feedback, as to how stupid
it was to ship non-working file sharing. I don't really think
whining helps all that much. On one occasion when it broke,
I got it sorta running again. As of today, it's OK again.

As far as I know, SSDP Discovery is a hood ornament, and
it's used to draw diagrams of servers on your net. It should
not affect basic file sharing. Someone else corrected me on
this in the past. I thought though, that the NetBIOS has
to be working, to find the other machine. Before SSDP was
invented, this stuff did work. And whatever passed for a
nameserver, had to work. SSDP is a more recent innovation,
on par with Bonjour.

Paul

On 05/03/2017 03:36 PM, Wolf K wrote:

[snip]

Try disconnecting the XP machine, then reconnecting it to the network.
I'd even a do reboot between disconnect/reconnect.

Good luck,


Sometimes it also helps to reset any network switches between the
machines. This can include the one in your router (reboot the router).

--
Mark Lloyd
http://notstupid.us/

"SENILE.COM found. Out Of Memory."

On 05/03/2017 05:47 PM, mike wrote:

[snip]

I've had connection issues that I fixed by:
shutdown all PC's
reboot router

The router itself isn't involved in local network communication, however
most units also include a network switch and 1 or more WiFi radios. If
these are involved, you want to reset them.


restart all PC's
Wait
And it eventually fixed itself.
There are actual network commands to do all that,
but I can't remember them when I need them, and
whatever I typed didn't fix the problem.

[snip]

--
Mark Lloyd
http://notstupid.us/

"SENILE.COM found. Out Of Memory."

On 04 May 2017, mechanic wrote in
alt.comp.os.windows-10:

Ha! Pity then that so many people have problems with this. As a
minimum to get things going I have to ensure all machines have an
account running with the same user name and password, and fix the
IP addresses rather than using DHCP and relying on machine names.

You have to have consistent user names and passwords across machines.
That is completely logical. None of that other stuff you mention is
necessary.

Check after reboot if networking is OK, if not then:
r enable NetBIOS over TCP/IP in the properties of IPv4, under the
WINS tab, within the properties of your network interface card.
type "services.msc"

Not enabled on my Win10 machine.

into the search box and hit enter,
confirm that the following services are started, consider setting
the startup type to automatic:

Computer Browser
Function Discovery Provider Host
Function Discovery Resource Publication
Network Connections

Not running on my Win10 machine.

Network List Service
Network Location Awareness
Network Store Interface Service
Server
SSDP Discovery
TCP/IP NetBIOS Helper
Workstation

Those are all enabled by default (expect maybe "Network Connections") -
there should be no action needed by the average user. If you've been
attempting to be clever by disabling services... well, it's your own
fault if things don't work as expected.

On Fri, 05 May 2017 00:22:43 -0400, Nil wrote:

You have to have consistent user names and passwords across machines.
That is completely logical.

No it isn't. You may have different login names on different
machines, why shouldn't you network them? I pointed out that things
go better if you have the same name/password on different machines.
I find that if you get networking going (by following some subset of
the pointers I listed) Windows may then afterwards run happily with
you using names to logon rather than IP addresses. Don't ask me why.

None of that other stuff you mention is necessary.

It's an assembly of tips from various sources. What works and what
doesn't is very much down to particular configurations of the
networked machines.

Note I didn't mention Homegroups, that may work but doubtful on a
network of mixed Win Vista,7,8,10 machines. Suck it and see if you
want!

...there should be no action needed by the average user...

Then they wouldn't be on here seeking solutions would they?

On 05 May 2017, mechanic wrote in
alt.comp.os.windows-10:

No it isn't. You may have different login names on different
machines, why shouldn't you network them?

If you are logged into one machine with a particular computer with one
ID and password and you try to connect to another machine where you
don't have an account, you should be prompted to supply credentials for
an valid account on that machine. That's how it works and has always
worked on my network

I pointed out that
things go better if you have the same name/password on different
machines.

True. If you keep accounts consistent across machines, you don't have
to hassle about inputting credentials.

I find that if you get networking going (by following
some subset of the pointers I listed) Windows may then afterwards
run happily with you using names to logon rather than IP
addresses. Don't ask me why.

I've never had to use IP addresses for other Windows machines, but I
sometimes have for Linux or Android devices..

None of that other stuff you mention is necessary.

It's an assembly of tips from various sources. What works and what
doesn't is very much down to particular configurations of the
networked machines.

OK. They're not general requirements for networking, though.

Note I didn't mention Homegroups, that may work but doubtful on a
network of mixed Win Vista,7,8,10 machines. Suck it and see if you
want!

I haven't bothered with Homegroups, since I know the traditional
Windows Networking works.

...there should be no action needed by the average user...

Then they wouldn't be on here seeking solutions would they?

Networking is a confusing concept for a lot of people, but I have yet
to find a home network that can't be made to work. Windows Networking
usually just works for me with little or no finagling. I haven't had a
lot of experience with introducing Windows 10 into a home network, but
my one Win10 computer networks easily and reliably here.

In article , rednoise9
@REMOVETHIScomcast.net says...

On 05 May 2017, mechanic wrote in
alt.comp.os.windows-10:

No it isn't. You may have different login names on different
machines, why shouldn't you network them?

If you are logged into one machine with a particular computer with one
ID and password and you try to connect to another machine where you
don't have an account, you should be prompted to supply credentials for
an valid account on that machine. That's how it works and has always
worked on my network

I pointed out that
things go better if you have the same name/password on different
machines.

True. If you keep accounts consistent across machines, you don't have
to hassle about inputting credentials.

I find that if you get networking going (by following
some subset of the pointers I listed) Windows may then afterwards
run happily with you using names to logon rather than IP
addresses. Don't ask me why.

I've never had to use IP addresses for other Windows machines, but I
sometimes have for Linux or Android devices..

None of that other stuff you mention is necessary.

It's an assembly of tips from various sources. What works and what
doesn't is very much down to particular configurations of the
networked machines.

OK. They're not general requirements for networking, though.

Note I didn't mention Homegroups, that may work but doubtful on a
network of mixed Win Vista,7,8,10 machines. Suck it and see if you
want!

I haven't bothered with Homegroups, since I know the traditional
Windows Networking works.

...there should be no action needed by the average user...

Then they wouldn't be on here seeking solutions would they?

Networking is a confusing concept for a lot of people, but I have yet
to find a home network that can't be made to work. Windows Networking
usually just works for me with little or no finagling. I haven't had a

Easier way for an in-house personal network is simply just create an
"Everyone" as one of the people can share the folder. Turn Off Password
required under Network & Sharing gives you access with nothing else
required.