@Tiebierius That checkbox for Verbose logging (General, Enable Plex Media Server Verbose Logging) is what I unchecked a week or so back.
I just found the Player logging, it was set to disabled. I set it to enabled, rather than Verbose.
In any case, the server logging has already been unchecked.
Just did an uninstall/reinstall. Should have a couple recordings this afternoon. Thanks again.
I forgot about the security change the requires you to restart your server if you change the logging settings.
@pl_5309 Thanks. I just rebooted it.
Attached are logs that include two recordings from yesterday. Jeopardy only recorded two minutes and Name That Tune only recorded one minute. Thanks again.
Was this with the firewall on or off?
May 17, 2022 16:00:38.442 [6552] ERROR - [Transcoder] [tcp @ 02ac93c0] Connection to tcp://192.168.1.24:5004 failed: Error number -138 occurred
Firewall is (was) turned back on. Only had it off yesterday while we swapped messages.
Looking at what you pulled from the logs has me seriously confused. Nothing has changed on the physical server, Plex server, and network. Why would that be happening all of the sudden?
Ugh. Very frustrating. Thanks again.
To add on, there are a couple other errors (below) associated with communications to/from 192.168.1.24. Am I correct that it is your HDHR tuner?
Have you looked at your HDHR device logs? I have a different HDHR model than you, but there should be a way to view your tunerās logs from the tunerās web interface. Look to make sure it isnāt getting network errors, reboots from the application watchdog, etc. In particular look for anything out of the ordinary around the times that recordings fail.
Also, in your Plex server web interface, check Settings ā Transcoder. Do you have a āTranscoder Temporary Directoryā set? If so, where is it? I know that setting the Transcoder Temp directory to a non-local/network drive can cause issues.
May 17, 2022 12:25:22.067 [9300] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/10A1369E at http://192.168.1.24:80
May 17, 2022 12:25:22.067 [9300] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/10A1369E was already known, refreshing database info
May 17, 2022 12:25:22.068 [9300] DEBUG - HTTP requesting GET http://192.168.1.24:80/discover.json
May 17, 2022 12:25:22.079 [9672] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 401 response from GET http://192.168.1.24:80/discover.json
May 17, 2022 12:25:22.079 [9300] DEBUG - JSON parse error: Invalid value. (0)
May 17, 2022 12:25:22.080 [9300] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/10A1369E, marking as dead.
May 17, 2022 12:25:22.080 [9300] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/10A1369E died
and
May 17, 2022 16:05:05.628 [10972] DEBUG - [Grabber/bca17853cb1ef7984ba986bdbe3da325f18e9552] Grabber: Signal information for tune on channel 5fc76e2a7a5882002d878d0d-5fc705f5c8d56d002e06f825: strength: 100, quality: 100
May 17, 2022 16:05:06.570 [10304] ERROR - [Transcoder] http://192.168.1.24:5004/auto/v36.1: I/O error
May 17, 2022 16:05:06.582 [8308] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe' exit code for process 8780 is 1 (failure)
Took a second look at the logs and came up with some additional rabbit holes to look at.
Possible bad/failing HDHOMERUN - the http 401 errors
Possible bad Windows update - havenāt found anything related yet
Possible tcp port exhaustion - Look for āEvent IDā 4227 using event viewer on the Windows System log
DNS issue - reboot router and flush server DNS
Problem with the Plex database - Delete the DVR and re-add
@pl_5309 @hokierulz Based on the info yāall gave me about the network failures seeming to be an issue I decided to make some changes there.
History: About six (6) months ago I replaced an aging Linksys E9400 AC5000 Tri-Band router with a mesh network Linksys Velop AX4200 3-node system. This was set up fairly basic. I only changed security for the router admin, and then created the Wi-Fi mesh network, and then set all the reserved DHCP addresses for my devices. Everything else was default. For quite some time this worked fine, including Plex. At some point a few weeks back this issue started. So was it a Plex update that created some conflict or a firmware for the Velop system? I donāt see any recent firmware updates for the Velop since initial setup so Iām thinking Plex.
This weekās setup: Based on yāalls input, on Wednesday, I replaced the āMeshā Velop AX4200 with a more traditional router, a Linksys E9450. Again, pretty basic setup; changed admin stuff, created Wi-Fi network, reserved addresses. Lo and behold, Plex recorded just fine. The short recording issues were gone and I had normal length recordings and commercial skip was working as expected. So thereās definitely something different between the defaults of the Velop router and the E9450.
Today: Not wanting to have wasted my money on the Velop system, and actually appreciating the Wi-Fi coverage, Iāve left the E9450 as the primary router, but turned off itās Wi-Fi and then set the Velop system in Bridge mode to use it for Wi-Fi only. Wi-Fi is the only thing this system is doing. All routing functions are done by the E9450. UGHHHH!!! With this configuration, Iāve just had my first recording of today fail again. 3 minutes of Ask This Old House was all it got.
What in Godās green earth could be causing a conflict with the Velop system, especially with it only serving in Bridge mode for Wi-Fi? This is driving me nuts.
So 1/2 later and This Old House is set to record. Iāve turned off the Velop nodes and set the E9450 back to normal with Wi-Fi on. And this recording also failed at 3 minutes. So now the Velop system is no longer on the network, and Plex recordings that were working are now back to not working.
Attached are logs from today. I literally donāt know what else to do. Thanks again.
Plex Media Server Logs_2022-05-21_11-16-17.zip (5.0 MB)
Just deleted the DVR. Rebooted the router. Rebooted the HD Homerun. Added the DVR back.
12:30 set up a recording of Kevin Boltonās Louisiana Cooking. It recorded for 4 minutes. I was watching activity and once it got to 3 minutes I thought I was good to go. Then at 4 minutes I got an onscreen (Windows screen in Plex) message that the recording was successful. Obviously it wasnāt successful at only 4 minutes
This feels like a network issue, but we havenāt been able to nail it down yet. Ideas:
It would be very helpful if you would look at your HDHR tuner logs at the time of a failure to see if there are any errors or additional info there. A good recording in my HDHR logs has three lines: One with tuning info, the next with streaming info, and the last with a stream ended message. If you see anything more it would be helpful if you would post what is in HDHR logs.
If you havenāt already I would suggest assigning both your HDHR tuner and your Plex server computer a manual IP address in your routerās DHCP settings.
It does appear from your logs that you still have IPv6 enabled in Plex. In Plex Web, try turning this off by going to Settings ā Network and uncheck āEnable server support for IPv6ā.
Are your Plex server and HDHR tuner wired or wifi? (I donāt think the HDHR tuners have wifi capability, but am not fully familiar with recent models.) Recording is very sensitive to any network issues or packet drops, so if everything can be wired at least for testing it would be very useful to try.
I see references to a NAS in your logs. Per my previous post, would you verify that you donāt have your transcoder temp directory on a network drive?
May 21, 2022 04:00:13.922 [9540] DEBUG - [HttpClient] HTTP simulating 408 after curl timeout
May 21, 2022 04:00:16.488 [8696] ERROR - [Transcoder] [tcp @ 02569e80] Connection to tcp://192.168.1.23:5004 failed: Error number -138 occurred
May 21, 2022 04:00:16.488 [8696] ERROR - [Transcoder] http://192.168.1.23:5004/auto/v18.1: Unknown error
@hokierulz Thank you again for trying to help.
I will have to do some research tomorrow on how to get logs off of the HDHR, but Iāll get them and add what I have.
Just about every single item on my home network is assigned a static IP address from the router. The Plex server is 192.168.1.8 and the HDHR is 192.168.1.24, Theyāve had these same IP addresses since the day I joined them to my network. I know I donāt have to give everything a static address, but I guess Iām just ā ā ā ā that way.
I just checked and indeed IPV6 was enabled. Its disabled now. Rebooted server.
Everything connected in reference to this issue is wired with gigabit CAT-6A cabling and gigabit switches,
I can confirm that the temp directory for this server is on the same local drive as the DVR, which as stated earlier is a 9TB RAID 5 array. Iāve verified the array is reporting healthy status. I do have two other Plex instances running on WD PR-4100 NASās, but they are not set up for Live TV & DVR. They are just local hosts for my personal media. This server only has the Live TV & DVR on said RAID drive.
Iām a bit confused by the error you quoted. That IP address (192.168.1.23) is my Xbox 360 in the living room. It shouldnāt have anything at all to do with this mess.
After turning off IPV6 I had the 9 oāclock news set up to record. It only recorded 3 minutes.
@hokierulz Not sure if this is related or completely non-related and another issue, or if its not an issue at allā¦
When I logged onto the server settings to check the IPV6 status, I had a green checkmark next to the Remote Access entry on the left menu.
When I went back to the server after the 3 minute recording of the news, it now says that Iām logged in but do not have remote access.
I havenāt change anything on that setting, and frankly most settings are just defaults.
FYI, unless HDHR has changed how to get to the web interface for their devices, then you can get there just by putting the tunerās IP address into your web browser (e.g. http://192.168.1.24 in your case.) For my HDHR Extend the logs are under the āSystem Menuā then āSystem Logā).
Are you sure that 192.168.1.24 is your HDHR tuner? Iām seeing a number of log entries in the latest logs you posted that suggest your HDHR tuner is at 192.168.1.23:
May 21, 2022 09:54:20.835 [3612] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/10A1369E at http://192.168.1.23:80
May 21, 2022 09:54:20.835 [3612] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/10A1369E was already known, refreshing database info
May 21, 2022 04:00:10.903 [11024] DEBUG - [Grabber/1e9ff75d562b1e0f4355bb988a5dade84c61091c] Grabber: Going to record for 1800 seconds, final URL is http://192.168.1.23:5004/auto/v18.1
192.168.1.23 is even responding to requests for tuner discovery and lineup status.
May 19, 2022 21:17:00.814 [9864] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.23 (HDHomeRun ATSC 10A1369E)
May 19, 2022 21:17:00.814 [10100] DEBUG - DVR:Device: Discovering and refreshing devices with identifier tv.plex.grabbers.hdhomerun
May 19, 2022 21:17:00.815 [10100] DEBUG - Grabber: HDHomerun discovered a model HDFX-4K.
May 19, 2022 21:17:00.815 [10100] DEBUG - HTTP requesting GET http://192.168.1.23:80/discover.json
May 19, 2022 21:17:00.821 [9540] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 200 response from GET http://192.168.1.23:80/discover.json
May 19, 2022 21:17:00.821 [10100] DEBUG - HTTP requesting GET http://192.168.1.23:80/lineup_status.json
May 19, 2022 21:17:00.834 [9540] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 200 response from GET http://192.168.1.23:80/lineup_status.json
May 19, 2022 21:17:00.864 [10100] DEBUG - Grabber: HDHomerun discovered a model HDFX-4K.
May 19, 2022 21:17:00.864 [10100] DEBUG - Grabber: HDHomerun discovered 1 compatible devices.
Try putting http://192.168.17.23/discover.json into your web browserā¦ see if it responds with info about your tuner.
If that really is the IP for an Xbox, then is there any chance you have multiple devices providing DNS on your network, or somehow otherwise both the Xbox and the HDHR tuner have the same IP? Having two devices assigned the same IP obviously would cause network instability for those devices.
@hokierulz @pl_5309 This morning I reset the router to factory defaults and set everything up as new. I reconfirmed the static IP addresses. I then went in to Plex and moved the temp directory to a different drive from the DVR directory.
Jeopardy just failed after 4 minutes.
I pulled the logs from the HD Homerun, but I canāt make heads or tails from most of it. There are errors about it talking to the server, DNS failures, and All Tuners in Use, which is weird as I donāt have any four simultaneous recordings scheduledā¦
19700101-00:00:01 System: reset reason = power on
19700101-00:00:02 System: network link 100f
19700101-00:00:03 System: ip address obtained: 192.168.1.24 / 255.255.255.0
20220521-16:38:50 System: time changed from Thu Jan 1 00:00:19 1970 to Sat May 21 16:38:50 2022
20220521-16:47:31 Tuner: tuner2 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-16:47:31 Tuner: tuner2 streaming http to 192.168.1.8:50349
20220521-16:48:05 Tuner: tuner2 http stream ended (remote closed)
20220521-16:52:50 Tuner: tuner2 tuning 54.1 KNVA-HD (8vsb:527MHz-3)
20220521-16:52:50 Tuner: tuner2 streaming http to 192.168.1.8:50621
20220521-16:53:28 Tuner: tuner2 http stream ended (remote closed)
20220521-17:30:01 Tuner: tuner2 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-17:30:01 Tuner: tuner2 streaming http to 192.168.1.8:50265
20220521-17:31:09 Tuner: tuner3 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-17:31:10 Tuner: tuner3 streaming http to 192.168.1.8:50402
20220521-17:33:42 Tuner: tuner0 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-17:33:42 Tuner: tuner0 streaming http to 192.168.1.8:50821
20220521-17:35:00 Tuner: tuner1 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-17:35:00 Tuner: tuner1 streaming http to 192.168.1.8:50974
20220521-17:36:00 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:36:15 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:41:18 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:42:20 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:42:28 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:42:28 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-17:44:05 HTTP: rejecting request from 192.168.1.10 - all tuners in use
20220521-17:44:47 HTTP: rejecting request from 192.168.1.10 - all tuners in use
20220521-17:46:19 Tuner: tuner2 http stream ended (remote closed)
20220521-17:48:51 Tuner: tuner3 http stream ended (remote closed)
20220521-17:50:08 Tuner: tuner0 http stream ended (remote closed)
20220521-17:51:07 Tuner: tuner1 http stream ended (remote closed)
20220521-17:51:10 Tuner: tuner2 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-17:51:10 Tuner: tuner2 streaming http to 192.168.1.10:53780
20220521-17:51:26 Tuner: tuner2 http stream ended (remote closed)
20220521-17:51:27 Tuner: tuner2 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220521-17:51:27 Tuner: tuner2 streaming http to 192.168.1.10:53785
20220521-17:51:33 Tuner: tuner2 http stream ended (remote closed)
20220521-17:58:54 Tuner: tuner2 tuning 18.2 KLRU-CR (8vsb:521MHz-4)
20220521-17:58:54 Tuner: tuner2 streaming http to 192.168.1.8:65352
20220521-18:00:22 Tuner: tuner3 tuning 18.2 KLRU-CR (8vsb:521MHz-4)
20220521-18:00:22 Tuner: tuner3 streaming http to 192.168.1.8:65492
20220521-18:00:49 Tuner: tuner3 http stream ended (remote closed)
20220521-18:00:50 Tuner: tuner3 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220521-18:00:50 Tuner: tuner0 tuning 18.1 KLRU-HD (8vsb:521MHz-3)
20220521-18:00:50 Tuner: tuner0 streaming http to 192.168.1.8:49239
20220521-18:00:50 Tuner: tuner3 streaming http to 192.168.1.8:49237
20220521-18:01:40 Tuner: tuner1 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220521-18:01:40 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-18:01:40 Tuner: tuner1 streaming http to 192.168.1.8:49281
20220521-18:01:51 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-18:02:42 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-18:02:51 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-18:02:51 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220521-18:15:11 Tuner: tuner2 http stream ended (remote closed)
20220521-18:16:29 Tuner: tuner3 http stream ended (remote closed)
20220521-18:16:29 Tuner: tuner0 http stream ended (remote closed)
20220521-18:17:31 Tuner: tuner1 http stream ended (remote closed)
20220521-20:40:15 System: myhdhomerun_sync: webclient error (dns failed)
20220521-20:51:08 System: myhdhomerun_sync: webclient error (dns failed)
20220522-02:00:00 Tuner: tuner2 tuning 42.1 CBS (8vsb:593MHz-1)
20220522-02:00:00 Tuner: tuner2 streaming http to 192.168.1.8:49728
20220522-02:01:08 Tuner: tuner3 tuning 42.1 CBS (8vsb:593MHz-1)
20220522-02:01:08 Tuner: tuner3 streaming http to 192.168.1.8:49804
20220522-02:02:35 Tuner: tuner0 tuning 42.1 CBS (8vsb:593MHz-1)
20220522-02:02:36 Tuner: tuner0 streaming http to 192.168.1.8:49980
20220522-02:03:57 Tuner: tuner1 tuning 42.1 CBS (8vsb:593MHz-1)
20220522-02:03:57 Tuner: tuner1 streaming http to 192.168.1.8:50102
20220522-02:15:56 Tuner: tuner2 http stream ended (remote closed)
20220522-02:17:24 Tuner: tuner3 http stream ended (remote closed)
20220522-02:18:46 Tuner: tuner0 http stream ended (remote closed)
20220522-02:19:54 Tuner: tuner1 http stream ended (remote closed)
20220522-13:06:34 System: myhdhomerun_sync: webclient error (dns failed)
20220522-13:15:36 System: myhdhomerun_sync: webclient error (dns failed)
20220522-13:25:38 System: myhdhomerun_sync: webclient error (dns failed)
20220522-13:35:18 System: myhdhomerun_sync: webclient error (dns failed)
20220522-13:45:28 System: myhdhomerun_sync: webclient error (dns failed)
20220522-13:56:25 System: myhdhomerun_sync: webclient error (dns failed)
20220522-14:05:57 System: myhdhomerun_sync: webclient error (dns failed)
20220522-14:15:28 System: myhdhomerun_sync: webclient error (dns failed)
20220522-15:59:08 Tuner: tuner2 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220522-15:59:09 Tuner: tuner2 streaming http to 192.168.1.18:49197
20220522-16:00:58 Tuner: tuner2 http stream ended (remote closed)
20220522-16:00:58 Tuner: tuner2 tuning 54.1 KNVA-HD (8vsb:527MHz-3)
20220522-16:00:58 Tuner: tuner2 streaming http to 192.168.1.18:49198
20220522-16:02:10 Tuner: tuner2 http stream ended (remote closed)
20220522-16:02:10 Tuner: tuner2 tuning 46.4 DABL (8vsb:491MHz-4)
20220522-16:02:11 Tuner: tuner2 streaming http to 192.168.1.18:49199
20220522-16:02:53 Tuner: tuner2 http stream ended (remote closed)
20220522-16:02:53 Tuner: tuner2 tuning 46.3 StartTV (8vsb:491MHz-3)
20220522-16:02:53 Tuner: tuner2 streaming http to 192.168.1.18:49200
20220522-16:03:51 Tuner: tuner2 http stream ended (remote closed)
20220522-16:03:51 Tuner: tuner2 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220522-16:03:52 Tuner: tuner2 streaming http to 192.168.1.18:49201
20220522-16:04:17 Tuner: tuner2 http stream ended (remote closed)
20220522-16:04:48 Tuner: tuner2 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220522-16:04:48 Tuner: tuner2 streaming http to 192.168.1.18:49202
20220522-16:04:53 Tuner: tuner2 http stream ended (remote closed)
20220522-21:44:20 System: myhdhomerun_sync: webclient error (dns failed)
20220522-21:53:29 System: myhdhomerun_sync: webclient error (dns failed)
20220522-22:04:20 System: myhdhomerun_sync: webclient error (dns failed)
20220522-22:13:32 System: myhdhomerun_sync: webclient error (dns failed)
20220522-22:23:09 System: myhdhomerun_sync: webclient error (dns failed)
20220523-02:00:01 Tuner: tuner2 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220523-02:00:01 Tuner: tuner2 streaming http to 192.168.1.8:61867
20220523-02:02:00 Tuner: tuner3 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220523-02:02:00 Tuner: tuner3 streaming http to 192.168.1.8:62153
20220523-02:03:28 Tuner: tuner0 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220523-02:03:28 Tuner: tuner0 streaming http to 192.168.1.8:62307
20220523-02:05:20 Tuner: tuner1 tuning 7.1 KTBC-HD (8vsb:177MHz-3)
20220523-02:05:21 Tuner: tuner1 streaming http to 192.168.1.8:62506
20220523-02:06:35 HTTP: rejecting request from 192.168.1.8 - all tuners in use
20220523-02:16:49 Tuner: tuner2 http stream ended (remote closed)
20220523-02:18:17 Tuner: tuner3 http stream ended (remote closed)
20220523-02:20:08 Tuner: tuner0 http stream ended (remote closed)
20220523-02:21:24 Tuner: tuner1 http stream ended (remote closed)
20220523-21:00:02 Tuner: tuner2 tuning 36.1 KXAN-DT (8vsb:515MHz-3)
20220523-21:00:02 Tuner: tuner2 streaming http to 192.168.1.8:56146
20220523-21:02:48 Tuner: tuner3 tuning 36.1 KXAN-DT (8vsb:515MHz-3)
20220523-21:02:48 Tuner: tuner3 streaming http to 192.168.1.8:56640
20220523-21:04:11 Tuner: tuner0 tuning 36.1 KXAN-DT (8vsb:515MHz-3)
20220523-21:04:11 Tuner: tuner0 streaming http to 192.168.1.8:56757
20220523-21:05:39 Tuner: tuner1 tuning 36.1 KXAN-DT (8vsb:515MHz-3)
20220523-21:05:39 Tuner: tuner1 streaming http to 192.168.1.8:56899
20220523-21:08:09 HTTP: rejecting request from 192.168.1.8 - all tuners in use
Now this is interesting! Would you pull and post your Plex logs again also? Right now we donāt have both Plex and HDHR logs for the same period.
What Iām seeing from these HDHR logs:
Edit addition: On your windows 192.168.1.8 computer, would you open a command window and execute āping -t 192.168.1.24ā? This is a continuous ping of your HDHR tuner. You want to always see "Reply from messages with short times - probably not more that 15ms or so on your LAN. If you see any timeouts or other messages then something isnāt right.
Finally figured this out. Iām currently recording the news and itās been recording for 40 minutes. Between this forum and the HDHR forum I finally got the suggestion that led to the issue resolution.
As stated earlier, I have almost everything on my network setup with a static IP address. I should clarify that everything I use to access the internet or do things with have static IP addresses.
It turns out that I did indeed have an IP address conflict. One of the Onkyo home theater receivers was set up locally for the same IP address that I was assigning to the HDHR through the routerās reservation table.
I have no recollection of ever setting this receiver up with a manual static IP address but sure enough it was set. I know for sure that that receiver was set up over a year and a half ago so what triggered the conflict at the beginning of April is a mystery.
Turning that setting off and letting it get a new IP address from the router freed up the IP address for the HDHR and now everything is back to what it was.
Holy crap I went through six weeks to figure this out. Iām embarrassed that something this simple was the issue. I was looking for a much more complicated problem and didnāt see this little issue. But having most things assigned an IP address I was not looking for this at all. And since that receiver was only turned on occasionally that exacerbated the irregularities and lack of consistency.
I pride myself in having set up my home network when we purchased this house five years ago and the network has been running fine until this issue came up. So I probably let my pride get in the way of looking for something so simple because I was certain there were no issues like this.
So learn from me to not overlook the simple things.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
