Products > Test Equipment

Rigol MSO5074 can ping but not connect

(1/1)

65roadster:
The title says it all really. I can ping my scope from my Windows machine but cannot connect to it via Ultra Sigma or Web Control. I came across this as I am trying to do the MSO5000 all options hack. I've not gotten to the point in the hack where I actually change anything in the scope, I'm just at the point of it being backed up and trying it connect using the python script.

Since this looks like a more general problem with the scope, not a problem with the hack script, I thought a separate thread was appropriate.

Firmware 1.3.3.0 (just upgraded today using USB stick, firmware from Rigol's site)
Subnet is 255.255.255.0
IP address is 192.168.1.10
Windows IP is 192.168.1.17
Ping response in 1ms
Web connect (putting 192.168.1.10 into my browser URL) just says unable to connect
Ultra Sigma reports "Insufficient location information or the device or resource is not present in the system" when I have it test the IP address.

Any help is appreciated.

thm_w:
This is DHCP or static IP you've set?
If its static IP, what is the DNS?
Try DHCP if you haven't already.

65roadster:
Thanks for the response, this is using DHCP, DNS is 192.168.1.1, the IP address of my cable modem / DHCP server.
I tried static IP, turned off auto IP config and set the DNS to 1.1.1.1 to see if that had any effect but it did not.

65roadster:
When rebooting my scope I noticed that my windows PC was still successfully pinging the IP address my scope displayed in it's configuration. There is something amiss there.

I connected my windows PC and the scope to an isolated router and assigned fixed IP addresses and was able to complete the "upgrade" process.

Now as to why the scope thinks it's connected to the network with an IP address that is already assigned to something else, when the scope is configured for DHCP, Auto IP, no static IP... I'll go troubleshoot that.

NE666:

--- Quote from: 65roadster on December 24, 2024, 05:48:47 am ---When rebooting my scope I noticed that my windows PC was still successfully pinging the IP address my scope displayed in it's configuration. There is something amiss there.

I connected my windows PC and the scope to an isolated router and assigned fixed IP addresses and was able to complete the "upgrade" process.

--- End quote ---

Seems very likely that you've an IP address conflict on your original network segment. Either your DHCP is at fault, or you've some statically assigned addresses somewhere that conflict.

Navigation

[0] Message Index

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod