DWC does not connect to PC browser

handyandy

Hi, I hope someone here can help with this, as it's beginning to annoy me! Everything used to work fine when using Chrome, I ran DWC from the browser with no problems. If I used Edge it would very occasionally fail to connect in a similar manner.

The only thing of note that has changed is that in late February I had a dispute with Micosoft re 365, I ended up removing that software and totally re-installing Windows 11 and all my apps.

I am now trying to re-commision my 3d printer that runs via a Duet 3 mini 5 controller and has a PanelDue display connected. There have been no changes at all since before.

My problem is that, now when I try to run DWC from the browser I constantly get the error message 'This site ca't be reached 192.168.1.102 refused to connect'. The PanelDue displays all the correct messages to say it has connected with WiFi to 192.168.1.102

Please, any help with this would be great.

droftarts

@handyandy I don't run Chrome, but I think this is likely to be a Chrome problem.

First, check that your PC can see the printer on the network. Open a 'Command Prompt' (use the windows search bar, type 'Command prompt' and it should show the Command Prompt application, click it) and type ping 192.168.1.102
Here's an example from Windows, showing that there is a response to the ping request:

C:\>ping 192.168.1.134

Pinging 192.168.1.134 with 32 bytes of data:
Reply from 192.168.1.134: bytes=32 time=2ms TTL=128
Reply from 192.168.1.134: bytes=32 time=3ms TTL=128
Reply from 192.168.1.134: bytes=32 time=3ms TTL=128
Reply from 192.168.1.134: bytes=32 time=3ms TTL=128

Ping statistics for 192.168.1.134:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\>

If that works, then this is probably a Chrome issue. I don't have specific advice, but googling "chrome can't access local ip" comes up with suggestions to clear the browser cache and downloaded files (also specifically for the printer's ip address), clear the google DNS cache, reset Windows Networking, or disable Chrome's website protection (in the Privacy settings).

Ian

handyandy

@droftarts Thanks for that.