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!
            
			
			
			
			
			
			
			
				
			
			
			Ethernet connection issue solved
- 
				Robert Smagala
- Posts: 2
- Joined: Tue Nov 06, 2018
- Location: Colmar
- Country: France
- Nickname: Bootcat
- Laser Machine Make or Type: Bodor
- Laser Power: 130W
- Laser Bed Size: 63"x39"
- Home Position: TR
- RDWorks Version: 8.01.18
- Windows Version: Windows 10
- Gene Uselman
- Posts: 2180
- Joined: Thu Jul 07, 2016
- Location: Suburban Minneapolis, Minnesota, US
- Country: USA
- Nickname: Gene
- Laser Machine Make or Type: QC
- Laser Power: 130W
- Laser Bed Size: 900x1300
- Home Position: TR
- Control Software: LIGHTBURN
- RDWorks Version: RDw .19 & Lightburn
- LightBurn Version: Latest
- Ruida Controller: RDC6442
- Windows Version: Win 10 Pro
- Accessories: I have a combining lenses, pin tables [homebuilt], honeycomb tables , wireless remote, Modifed Ultimate Air Assist, home built non-powered rotary device, PrusaMK4 and Mini Prusa printers.
Welcome Robert and thanks for your solution. RDworks has always been flakey about communications and is one of the reasons many  of us have switched over to Lightburn which was written by one of our members in the USA who has a better understanding of our systems and will respond to questions and suggestions. Gene
            
			
			
			
			
			
			
			
				If the Help and advice you received here was of VALUE...
Please consider making a donation to maintain the RDWORKSLAB Forum.
The days that I keep my gratitude higher than
my expectations, Well, I have really good days.
Ray Wylie Hubbard- unfortunately deceased
			
			
			Please consider making a donation to maintain the RDWORKSLAB Forum.
The days that I keep my gratitude higher than
my expectations, Well, I have really good days.
Ray Wylie Hubbard- unfortunately deceased
- 
				Robert Smagala
- Posts: 2
- Joined: Tue Nov 06, 2018
- Location: Colmar
- Country: France
- Nickname: Bootcat
- Laser Machine Make or Type: Bodor
- Laser Power: 130W
- Laser Bed Size: 63"x39"
- Home Position: TR
- RDWorks Version: 8.01.18
- Windows Version: Windows 10
Gene,
Actually Lightburn had the same issue of connectivity in my case and it was solved when I set the static IP address.
I agree that it's a way better program than RDWorks.
            
			
			
			
			
			
			
			
				
			
			
			Actually Lightburn had the same issue of connectivity in my case and it was solved when I set the static IP address.
I agree that it's a way better program than RDWorks.

