Windows 10: LAN comms lost between Win7 PC & new Asus Win10 laptop after 1-2 hours

I cannot maintain communication between my Windows 7 PC and a new Asus laptop running Windows 10. I am using a LAN with a Work group on Win 7 and a Private network on Win 10. NOTE: I am a complete novice on Windows 10 but very experienced on Windows 7.

Initially, after I start the laptop, I can access the laptop using Windows Explorer or TightVNC but after one to two hours I lose contact. After re-establishing contact, I lose it again after an another hour or two.

The laptop can be left with the lid open and a program running (recording from a webcam) or left idle - it makes no difference. The power settings are for turn off display, sleep and hibernate, all set to "never"

I can only re-establish comms by switching the laptop's WiFi connection off and then on again - which requires access to the laptop.

When I "lose" contact, the PC under Windows 7 still lists the laptop but does not access it - i.e. Windows Explorer lists the laptop but when the name is clicked on, it says "Windows cannot access \\LAPTOP. Check the spelling ..."

Similarly, TightVNC cannot access it giving the error message "Error in TightVNC Viewer: A connection attempt failed because the connected party did not properly respond after a period of time ..." If TightVNC is left on, it still loses the link.

On the laptop, when I click on "Network" under Windows Explorer, it only lists the laptop itself - it doesn't see any of the others. However, TightVNC on the laptop can connect to the other laptops on the LAN but not to the PC.

This may not sound a major problem but I want to keep the laptop in a waterproof container and place it up in a tree to monitor wildlife - so I will not be able to access it to renew communications.

The reason this problem is only occurring now is that all my previous laptops were Mecer laptops running Windows 7 or Acer laptops running Windows 8.1 (3 are still running) and I have never encountered this problem before.

Given the fact windows can see it but not detect it makes me think it is either an Asus issue or a Windows 10 issue - Tight VNC is innocent in this case.

The Laptop is an ASUS VivoBook X540MA running Windows 10 Home Single Language (x64) Version 1909 (build 18363.418) and will continue to do so - once it is placed in the tree it will only be connected by WiFi on my LAN isolated behind a Comodo Firewall without any access to the internet.

The PC is an Asus H97M-PLUS motherboard with 32 GB RAM and a 2TB HDD with a further 3 8TB drives, so has more than enough capacity - running Windows 7 Professional (x64) Service Pack 1 (build 7601).

Both run TightVNC version 2.7.10.0.

:)

 

VB6 on Win10

Hello All,

I have an EXE which was written in VB6 edition. It uses a "Comm Port" and lists all the available COMM ports of the system in a drop down. This EXE works well on Win7 and Win8.

But, when we use this EXE (developed in VB6) on Win10 OS, then dropdown containing the list of COMM ports is empty (even if the computer has few COMM ports available).

We have another EXE developed in VB2010 edition. This EXE lists all the COMM ports in a dropdown on: Win7, Win8 and Win10.

But, an EXE developed in VB6 doesn't work on Win10.

My expectation:

1. Can we "somehow" make an EXE (written in VB6) to list all available COMM ports on Win10 OS?

2. If above is not possible, then what is an alternate solution for it?

~

 

WIN10 HOMEGROUP not accessible by WIN7 PCs

Hello,

I cannot connect my WIN 7(home) PCs (3 of them) to a homegoup created on a new Windows 10 (home) computer.

The WIN 7 PC see each other without any issue.

Here’s how I proceeded:

• Leave all homegroups on the WIN7 PCs
• Create a new homegroup on the WIN10 pc with the same group
• The WIN7 PCs see the new homegroup
• Click on join and enter password
• After some time I get a message that connection was not possible

I’ve also tried to create the homegroup on a WIN7 pc. The WIN10 pc can see and accept to join but the shares are not visible.



Running WIN 10 1709 HOME

 

access to win10 pc from win7 pcs on lan


A LAN has two win7pro pcs, a new win10Home laptop (replacing an older machine) and other laptops. The two win7pro pcs and the new win10 laptop form a development system for database/app/webapp software, and must be able to create & write files to most any folder on any of the three machines, anytime.


Essentially, we must be able to treat these three machines as if they were just one machine with several drives run by multiple instances of an admin user. That's how we work.


I can hear the corporate intakes of breath. For this request, lose that mindset: we're a family, not a corporation.


When the win10 laptop was configured and introduced to the network a few weeks ago, we managed to persuade it---against its corporate wishes---to allow such access without authentication requests.


Now, the win10 instance has updated itself, and since then, both win7 pcs encounter username & password requests on attempting to access the win10 laptop's drive c:. That stops us cold.


Worse, when the username & password are entered, we meet a further Orwellian requirement for a password for the drive on win7 machine from which the request was made!


How do we defeat these ludicrous requirements?