Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, April 29, 2019 9:54 PM
Hi!
I am copying my issue here in a forum:
" This is good enough to summarize everything:
Machine 1 LTSC Machine
Machine 2 W7 Enti
Machine 3 W7 Pro
Machine 1 can see the other 2 machines but can not connect to either of them.
The machine 2 can see both and can join.
Machine 3 only sees machine 2 and can connect to it.
If I use W7 Pro, W10 Pro or LTSB on machine 1, then I can connect to both machines, so any hardware or software fault is excluded because there are the same drivers and 2-3 programs on it.
It is also odd that machine 3 will never see machine 1 on any system I have on it ... "
Yesterday I pumped the same LTSC on machine 2 and only 1 can see 2 (not himself) but can't connect, 2 doesn't see 1 (only own himself).
If we only look at the first two machines now, if they both have LTSC then they can't connect to each other if I cross the W10 pro on the first machine then I can connect to machine 2, but still with machine 2 first, if I go back to W7 on Machine 2, I can only connect from Machine 1 if W7 Pro on Machine 1 on W7 Enti is good back then, but here is also illustrated :
LTSC - LTSC (unable to connect)
W10 pro > LTSC
W10 pro > W7 Enterprise
W7 Pro <> W7 Enterprise
LTSC can't connect to anything, is this function full dead?
All replies (3)
Tuesday, April 30, 2019 7:40 AM
Hi,
Could you please help me confirm what 'connect to' means? Do you mean access share folders?
If so, no matter the version of your windows, they all should support this function.
Did you try input \<ipaddress> in the address bar of file explorer? This can rule out the possibility of DNS or NETBIOS.
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, April 30, 2019 8:22 PM
"Do you mean access share folders?" - Yes
Input IP adress in file explorer not work.
Network discovery ON
Public Folder sharing ON
SMBv1 Enabled
Upnp Enabled
Example: Machine 3(win7 pro) can't not see if machine 1 on W10 LTSC, but if machine 1 W10 is visible.
Friday, May 3, 2019 2:24 AM
Hi,
If \<IPaddress> can't work, this means it can't access the share file,so it is not displayed.
For those computers which are not displayed, in their own file explorer, please try access \127.0.0.1, see if you can find the share file.
If so, then the connection from other computers to this one is broken, check firewall or route.
If not, then the server's SMB function is broken, check if service'Lanmanworkstation' is running.
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].