Help

On Thu, 4 Jul 2019 08:45:12 +0200, Arie de Muynck
wrote:

On 2019-07-04 01:15, Keith Nuttle wrote:
I was trying to troubleshoot a problem with with my LAN.* My laptop can
send and receive files from my desktop, but my desktop can not send and
receive files from the laptop.** When I try it says the desktop does not
have permission to the laptop.* While I checked many things to my
knowledge I changed NOTHING.

That seems to be a usual problem when:
- One of the computers is on a wired and the other on a WiFi connection
to the same LAN
- One or more computers are multi-homed (connected to one or more LANs),
either by having multiple LAN cards or by setting up a LAN card with
multiple IP address ranges.

This can be seen using Wireshark: the SMB protocol stack selects the
wrong address range for advertising.
When you need both, like me, you are really screwed. Windows used to
have a setting to set the priority of cards, and/or the IP ranges, but
that has been removed in Win10. There is probably a register trick but I
haven't found it yet. Probably I'll have to use the laptop on a wired
LAN, and on the main PC use a batch file to turn off the other LAN cards
and IP ranges temporarily when sharing files. Or use the cloud, or
sneaker-net...

Don't use multiple LANs.

Regards,
Arie

On Thu, 4 Jul 2019 09:20:35 +0200, Arie de Muynck
wrote:

Sorry Keith,
that answer was for the 'computer not found problem'.
You have the 'user not found' problem.

The user needs to have an account on the remote computer to access
files. E.g. I have made an account for user 'backup' on each computer to
allow backup of remote files from a central PC..

Arie

Don't top post


On 2019-07-04 08:45, Arie de Muynck wrote:
On 2019-07-04 01:15, Keith Nuttle wrote:
I was trying to troubleshoot a problem with with my LAN.* My laptop
can send and receive files from my desktop, but my desktop can not
send and receive files from the laptop.** When I try it says the
desktop does not have permission to the laptop.* While I checked many
things to my knowledge I changed NOTHING.

That seems to be a usual problem when:
- One of the computers is on a wired and the other on a WiFi connection
to the same LAN
- One or more computers are multi-homed (connected to one or more LANs),
either by having multiple LAN cards or by setting up a LAN card with
multiple IP address ranges.

This can be seen using Wireshark: the SMB protocol stack selects the
wrong address range for advertising.
When you need both, like me, you are really screwed. Windows used to
have a setting to set the priority of cards, and/or the IP ranges, but
that has been removed in Win10. There is probably a register trick but I
haven't found it yet. Probably I'll have to use the laptop on a wired
LAN, and on the main PC use a batch file to turn off the other LAN cards
and IP ranges temporarily when sharing files. Or use the cloud, or
sneaker-net...

Regards,
Arie

On 2019-07-05 13:32, Lucifer wrote:
Don't use multiple LANs.

Please Lucifer,

Enlighten me how to test the behavior of rogue equipment (like 'calling
home') without such a setup? And don't start about port mirroring on
switches, I don't like to pass data before it has been analyzed.

Arie

Arie de Muynck wrote:
On 2019-07-04 01:15, Keith Nuttle wrote:
I was trying to troubleshoot a problem with with my LAN. My laptop
can send and receive files from my desktop, but my desktop can not
send and receive files from the laptop. When I try it says the
desktop does not have permission to the laptop. While I checked many
things to my knowledge I changed NOTHING.

That seems to be a usual problem when:
- One of the computers is on a wired and the other on a WiFi connection
to the same LAN
- One or more computers are multi-homed (connected to one or more LANs),
either by having multiple LAN cards or by setting up a LAN card with
multiple IP address ranges.

This can be seen using Wireshark: the SMB protocol stack selects the
wrong address range for advertising.
When you need both, like me, you are really screwed. Windows used to
have a setting to set the priority of cards, and/or the IP ranges, but
that has been removed in Win10. There is probably a register trick but I
haven't found it yet. Probably I'll have to use the laptop on a wired
LAN, and on the main PC use a batch file to turn off the other LAN cards
and IP ranges temporarily when sharing files. Or use the cloud, or
sneaker-net...

Regards,
Arie

AFAIK, metrics for LANs are still available.

https://www.tenforums.com/tutorials/...dows-10-a.html

There's probably routing rules too, somewhere...

https://superuser.com/questions/1355...-and-route-add

Paul

On 2019-07-05 20:05, Paul wrote:
Arie de Muynck wrote:

... about computers not seeing each other...

That seems to be a usual problem when:
- One of the computers is on a wired and the other on a WiFi
connection to the same LAN
- One or more computers are multi-homed (connected to one or more
LANs), either by having multiple LAN cards or by setting up a LAN card
with multiple IP address ranges.

This can be seen using Wireshark: the SMB protocol stack selects the
wrong address range for advertising.
When you need both, like me, you are really screwed. Windows used to
have a setting to set the priority of cards, and/or the IP ranges, but
that has been removed in Win10. There is probably a register trick but
I haven't found it yet. Probably I'll have to use the laptop on a
wired LAN, and on the main PC use a batch file to turn off the other
LAN cards and IP ranges temporarily when sharing files. Or use the
cloud, or sneaker-net...

Regards,
Arie

AFAIK, metrics for LANs are still available.

https://www.tenforums.com/tutorials/...dows-10-a.html


There's probably routing rules too, somewhere...

https://superuser.com/questions/1355...-and-route-add


Â*Â* Paul


Thanks Paul,

That info may solve the problem. The trick is in the manual route
command, I used that before becoming lazy, using GUIs, and completely
forgot it can also set a metric:

route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
^^^^^^^^

I'll start testing that hoping SMB really checks for that metric!

Arie

Paul replied:
M$'s updates are a nightmare.

I find most of the time, using a Catalog.Update.Microsoft.COM
version of a KBxxxxxxx update (a .MSU file), most always
clears a logjam.

The situation is "manageable", but hardly a reason
for an Oscar trophy.

Now the people who leave their failed updates in a
big pile, and you find two years worth of failures...

I like to update my Windows 10 PC every 6 months or so.
For 6 months, I couldn't update it ( v1803 ).

My solution was to download+install v1903
( C:\Windows10Upgrade\Windows10UpgraderApp.EXE );
after which, I had to rename the "Documents" folder back to "Sys",
as that's what I always call it.

Also, I had to re-take ownership of "DefaultMediaCost" -Manually-,
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]
Re-Merge-In my settings ( Jeff-Relf.Me/Win10.REG.TXT ),
check for updates, ReBoot, and -Manually- change .JPG and .PNG file
associations using "Open With".

Also, I had to re-format all of my File-Explorer folders,
so they look the way I want. Likely, I'm doing something(s) wrong.