Ethernet connection issue solved
Posted: Thu Jul 08, 2021
Hello,
First of all thanks to the contributors of this forum - it helped me greatly at different times.
I'd like to contribute a solution to a nagging problem we have in our shop.
Our issue was intermittent connectivity problems through Ethernet between our different PCs under Windows 10 and our Bodor laser.
I won't give you the full detailed configuration because it's irrelevant for the solution I just found.
Anyhow, we have had trouble establishing an Eth connection between the 3 PCs running RDWorks and the laser.
Most of the time the issue went away after 2-3 reboots of both PC and laser.
The issue appeared sometime last year after one of the major Windows 10 updates.
We've always been able to ping the IP address of the laser from all the PCs.
Frustratingly, we can have a good connection from PC A and no connection from PC B or the reverse.
Solution: the new production PC connects flawlessly once setup with a static IP address.
To do that you would need to access the network adapter configuration in Windows 10 and change the network configuration from DHCP to manual.
Use an IP address outside the DHCP range, all other info is copied from the DHCP configuration info.
I would add that the static Eth configuration of the network card is exactly the same as what the DHCP server would give it otherwise so no idea what's causing our issue. Whether using an Orange fibre box or a Synology DNS the problem would remain.
Since I didn't find this particular problem addressed in the forum I thought I would for once contribute one myself.
Cheers!
First of all thanks to the contributors of this forum - it helped me greatly at different times.
I'd like to contribute a solution to a nagging problem we have in our shop.
Our issue was intermittent connectivity problems through Ethernet between our different PCs under Windows 10 and our Bodor laser.
I won't give you the full detailed configuration because it's irrelevant for the solution I just found.
Anyhow, we have had trouble establishing an Eth connection between the 3 PCs running RDWorks and the laser.
Most of the time the issue went away after 2-3 reboots of both PC and laser.
The issue appeared sometime last year after one of the major Windows 10 updates.
We've always been able to ping the IP address of the laser from all the PCs.
Frustratingly, we can have a good connection from PC A and no connection from PC B or the reverse.
Solution: the new production PC connects flawlessly once setup with a static IP address.
To do that you would need to access the network adapter configuration in Windows 10 and change the network configuration from DHCP to manual.
Use an IP address outside the DHCP range, all other info is copied from the DHCP configuration info.
I would add that the static Eth configuration of the network card is exactly the same as what the DHCP server would give it otherwise so no idea what's causing our issue. Whether using an Orange fibre box or a Synology DNS the problem would remain.
Since I didn't find this particular problem addressed in the forum I thought I would for once contribute one myself.
Cheers!