Having a problem getting 2 DCR-2650's working at the same time.
If I have both connected, they look good in "device settings", and channel listings (4 sources) but I can only record from 1 of them.
The second one would have you believe it's working if you look at the TV Guide, but no indicator lites are lit on the unit and nothing is actually being recorded.
If I only connect one at a time they both work fine.
I read in another post about manually entering the tuners in the registry, but I thought the Nshared.DLL solved that problem?
In any event I didn't see anything like that in the registry.
I have vague idea what is causing this. It relates to the detection of the ip address of the device.
Can you run 'ipconfig /all' and post the output?
Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\John>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : NEXTPVR
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : BDI-DOMAIN
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hauppauge WinTV-DCR-2650 (Model 143xxx) #
2
Physical Address. . . . . . . . . : 00-0D-FE-7E-40-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e4de:9774:5bbb:a83c%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.200.186(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Lease Obtained. . . . . . . . . . : Monday, November 25, 2013 2:54:38 PM
Lease Expires . . . . . . . . . . : Thursday, January 01, 2150 10:52:16 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.200.185
DHCPv6 IAID . . . . . . . . . . . : 452988414
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-25-4A-C1-D0-27-88-02-23-99
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hauppauge WinTV-DCR-2650 (Model 143xxx)
Physical Address. . . . . . . . . : 00-0D-FE-7E-09-61
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f867:97cd:9fc5:d6e8%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.231.138(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Lease Obtained. . . . . . . . . . : Monday, November 25, 2013 2:58:13 PM
Lease Expires . . . . . . . . . . : Thursday, January 01, 2150 10:52:16 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.231.137
DHCPv6 IAID . . . . . . . . . . . : 385879550
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-25-4A-C1-D0-27-88-02-23-99
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : BDI-DOMAIN
Description . . . . . . . . . . . : Intel® Gigabit CT Desktop Adapter
Physical Address. . . . . . . . . : 00-1B-21-42-47-DE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bdb1:19cd:de21:fe1d%13(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.35(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, November 25, 2013 2:54:38 PM
Lease Expires . . . . . . . . . . : Thursday, November 23, 2023 2:54:38 PM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 301996833
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-25-4A-C1-D0-27-88-02-23-99
DNS Servers . . . . . . . . . . . : 10.0.0.1
Primary WINS Server . . . . . . . : 10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168D/8111D Family PCI-E Gigab
it Ethernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : D0-27-88-02-23-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.BDI-DOMAIN:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : BDI-DOMAIN
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{DE8B5A98-9F86-469D-A664-1DB6358D63D5}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:34c4:2313:f5ff:ffdc(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::34c4:2313:f5ff:ffdc%15(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{82E0463F-41EB-469D-BEE5-4E12D936DF10}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{EDDAAE91-BCDF-485B-8744-3454B7E899DE}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\John>
Thanks.
Can you also visit the Settings->Devices screen, and post the npvr.log?
Unfortunately I don't have both tuners connected at this time.
I needed to split them to do my nightly recordings.
In any event, I'm including a file that may have what you're looking for.
If not, I'll do it over in the morning.
Thanx.
Just in case the first log didn't have what you asked for, I reran it this morning with the commands you gave me.
I realize you're a pretty busy guy, and I read that you're getting ready to leave for awhile, but if there's anyway you could whip up a quick fix before you go I would be most appreciative.
As it is now, I'm running 2 separate systems in order to record the shows I need.
Once again, thanx for looking at this and all the help you've given me already!
Here is a temporary patch you can try.
With this patch, you can try overriding the IP detection using a c:\users\public\npvr\forcedip.xml, containing something like this:
Code:
<devices>
<device id="201200AA">192.168.230.138</device>
<device id="20104B0C">192.168.200.186</device>
</devices>
NOTE: I'm not sure these are the correct values for your setup. They may need to be swapped.
SWEET!
Am recording 4 different shows on the same server.
A quick test looks good; I'll report back if I find any problems.
As you expected, I had to swap the values.
Actually I had to change one of them.
I guess it got a different IP because I had it the other server overnite.
Just curious; will this patch be incorporated into the main app, or do I need to keep track of these files?
jrockow Wrote:Just curious; will this patch be incorporated into the main app, or do I need to keep track of these files?
It is in the main app until I find a way to replace it with something better. Ideally the app would be able to do it automatically, but unfortunately it cant at the moment. The same problem does not happen with the SiliconDust versions of the device.