W10 LAPPY >>>>> W7 LAPPY: nope W10 LAPPY <<<<< W7 LAPPY: yes Android Phone >>>>> W7 LAPPY: nope Android Phone >>>>> W10 LAPPY: yes Computer's name is visible but as soon as I click on it the error dialog shows up. Problem lies on W7 LAPPY obviously. I did everything usually I do to share a folder over a home network. This laptop was formatted and reinstalled by me months back last year and never used it and it was stored in a closet until now that I'm in need. This network issue was present since day 1 but never truly followed up. Fwiw I can browse the internet without issues
Throw your two cents over the table, promise not to bite An alternative to Windows network protocols to share a folder? Does such a software even exist?
Already tried disabling it, fully. But gonna try again and I'll be back to edit this post. Edit: didn't work out.
#1 The shared folders are visible form the w7 machine itself? #2 \\<ip of the w7 machine>\share works ? #3 any antivirus\antimalware that may interfere? #4 any clue on w7 logs if you stop and restart the server service? (is the server service running anyway?)
Yes they are. You nailed it. It worked out. Great. Never ever had this issue before. It worked browsing from W10 machine. Need to try from mobile. None. It's actually running, manual start.
192.168.0.1 Is your router's IP I presume. If that's correct Just try (from W7, as administrator) Ipconfig /flushdns ipconfig /registerdns If that's wrong, just fix it It could be also the DNS server crashed on your router, if the above doesn't work try to reboot your router and try again.
I forgot to say this laptop was formatted and reinstalled by me months back last year and never used it and it was stored in a closet until now that I'm in need. This network issue was present since day 1 but never truly followed up. Did the ipconfig thing no success. Fwiw I can browse the internet without issues.
Try to do the ip thing on w10 machines as well look for any bogus entry on \windows\system32\drivers\etc\hosts (the stock one should have just the localhost entry) Take a look to the configuration webpage of the router if you see the machine name or just the ip of the affected machine or of any meaningful difference between the machines (this varies a lot depending on the router brand/age) try if disabling the ipv6 helps As a last resort try to remove the network card from the device manager, then redetect it (or reboot), then reconfigure it if not on dhcp
Uh... I'm getting short of ideas I assume your router is acting also as DHCP then if you don't set the static IP the W7 machine gets a meaningful IP configuration?
Correct. Lappy has two network adapters, one wireless the other wired Ethernet. Wireless adapter has static IPs Ethernet adapter dynamic IPs I've tried both adapters one at a time disabling the other. Something's wrong at an upper layer.
Due to this issue I had to do this. Luckily it was resolved, now network shares are fully functional again and got more good "side effects" applying simplix pack and abbodis add-ons.
It had. That install was made with a custom iso integrating updates from a simplix pack dating back to 2018 or 2019. From a security pov I acknowledge that Windows was insecure but network troubles for not being fully up to date?
If you were updated to 2019, yes hardly that was the cause. But the custom ISO part maybe went wrong on some small detail. That's why I'm used to keep handy a bunch of native vhds, deployed from the official ISO and updated traditionally. Then all I need to do is copy one of such vhds to the machine (or virtual machine) add it to bootloadder using bootice, and I'm done. A lot of time spent once, a huge amount of time spared on each new install. I think its ten years that I don't install on a partition, not even using XP
>Something's wrong at an upper layer. Yes ......... cool that you finaly and ireversably admit it .......... in public