NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Legacy (v4.x and earlier) v
« Previous 1 … 184 185 186 187 188 … 433 Next »
Clients taking ages to start(30sec)

Clients taking ages to start(30sec)
imilne
Offline

Posting Freak

Posts: 2,423
Threads: 135
Joined: Feb 2008
#31
2013-04-06, 11:42 AM
Just tried it on a freshly installed (Windows and NPVR) desktop that's on gigabit wired and startup was near instant. I'll double check with a wired connection on my laptop, but that suggests it might be a plugin issue, and the only ones on that laptop are my own :eek:

Iain
jpsa
Offline

Member

Posts: 65
Threads: 9
Joined: May 2011
#32
2013-04-07, 10:05 PM
Just a quick note to say that I'm seeing slow client startup too, but in my case it wasn't 2.6.2 which caused it, it was upgrading both client & server to W7 from XP. I'd assumed it was probably firewall related, but haven't got round to investigating further yet.
jpsa
Offline

Member

Posts: 65
Threads: 9
Joined: May 2011
#33
2013-04-09, 10:29 AM
jpsa Wrote:I'd assumed it was probably firewall related, but haven't got round to investigating further yet.
OK, I've done a little investigation, and I'm still puzzled! Here's an extract from the client logs from a slow startup
Code:
:
2013-04-09 11:13:00.994    [DEBUG][1]    Load@7
2013-04-09 11:13:05.527    [INFO][3]    Checking online for updated versions...
2013-04-09 11:13:05.527    [INFO][3]    Web@1
2013-04-09 11:13:05.895    [INFO][3]    Online check reports version info:
<version><component name="NextPVR" version="2.6.2" display="NextPVR 2.6.2"><url>http://forums.nextpvr.com/showthread.php?53816-2-6-2-available-(March-24th)</url></component></version>
2013-04-09 11:13:05.896    [INFO][3]    current online version: 2.6.2
2013-04-09 11:13:05.896    [INFO][3]    last notified version: 2.6.2
2013-04-09 11:13:22.009    [DEBUG][1]    Load@8
:
I can confirm that turning off the Windows firewall on the server cures the problem. However, the firewall is already configured to allow NRecord.exe full access. In addition, turning on firewall logging apparently shows no rejected connection attempts.
Code:
2013-04-09 10:58:29 ALLOW UDP 192.168.0.4 255.255.255.255 138 138 0 - - - - - - - RECEIVE
2013-04-09 10:58:30 ALLOW UDP fe80::95c5:4952:2041:efdd ff02::1:3 62988 5355 0 - - - - - - - RECEIVE
2013-04-09 10:58:30 ALLOW UDP 192.168.0.2 224.0.0.252 63011 5355 0 - - - - - - - RECEIVE
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 62988 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP 192.168.0.5 192.168.0.2 5355 63011 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 64307 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 60299 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP 192.168.0.5 192.168.0.2 5355 61765 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 51171 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW TCP fe80::95c5:4952:2041:efdd fe80::1ce4:15c9:9fcd:aa81 51566 445 0 - 0 0 0 - - - RECEIVE
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 57523 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP 192.168.0.5 192.168.0.2 5355 61337 0 - - - - - - - SEND
2013-04-09 10:58:30 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 fe80::95c5:4952:2041:efdd 5355 60802 0 - - - - - - - SEND
2013-04-09 10:58:38 ALLOW UDP 192.168.0.1 239.255.255.250 1900 1900 0 - - - - - - - RECEIVE
2013-04-09 10:58:47 ALLOW UDP 127.0.0.1 239.255.255.250 1900 1900 0 - - - - - - - SEND
2013-04-09 10:58:47 ALLOW UDP 192.168.0.5 239.255.255.250 1900 1900 0 - - - - - - - SEND
2013-04-09 10:58:47 ALLOW UDP ::1 ff02::c 1900 1900 0 - - - - - - - SEND
2013-04-09 10:58:47 ALLOW UDP fe80::1ce4:15c9:9fcd:aa81 ff02::c 1900 1900 0 - - - - - - - SEND
2013-04-09 10:58:51 ALLOW TCP 192.168.0.2 192.168.0.5 51569 8968 0 - 0 0 0 - - - RECEIVE
(this firewall log from a different session to the client log above).

Can anyone knowledgeable give me any clues about what NPVR does just prior to the Load@8 log entry, so I have some idea where to look next?
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,807
Threads: 769
Joined: Nov 2003
#34
2013-04-09, 05:07 PM
jpsa Wrote:Can anyone knowledgeable give me any clues about what NPVR does just prior to the Load@8 log entry, so I have some idea where to look next?

Between "Load@7" and "Load@8", the client makes it's first network request to the server, making a simple call to ask what the list of available record directories are configured on the server. Its not passing a lot of data, just a simple string of text.
jpsa
Offline

Member

Posts: 65
Threads: 9
Joined: May 2011
#35
2013-04-09, 11:26 PM
sub Wrote:Between "Load@7" and "Load@8", the client makes it's first network request to the server...
Thanks!

I have a bit more information: as you suggested near the top of this thread, I tried replacing the server name ("laphroaig") with an ip address ("192.168.0.5") and that was enough to cure the problem here, even though the firewall was still active. I note this differs from stustunz's reported experience.

I'm still not sure why there's a problem, though: executing "ping laphroaig" on the client works instantly, so there's no general delay in resolving names.
Zeb
Offline

Senior Member

U.S.A.
Posts: 596
Threads: 2
Joined: Dec 2012
#36
2013-04-10, 12:42 AM
imilne Wrote:Just tried it on a freshly installed (Windows and NPVR) desktop that's on gigabit wired and startup was near instant.

@imilne: I notice that this problem is as un-American as h.264. Did you update Windows (including the infamous platform update) before installing NPVR (or at least before Patch 2), or did you patch first and update Windows later on your freshly-installed desktop?

@jpsa: Same question with respect to your upgrade to Windows 7: Did you update Windows 7 first or install Patch 2 first? Granted, this very likely has nothing to do with the problem.
imilne
Offline

Posting Freak

Posts: 2,423
Threads: 135
Joined: Feb 2008
#37
2013-04-10, 07:08 AM
Zeb Wrote:@imilne: I notice that this problem is as un-American as h.264. Did you update Windows (including the infamous platform update) before installing NPVR (or at least before Patch 2), or did you patch first and update Windows later on your freshly-installed desktop?

Windows got all its updates before NPVR went on.

I still haven't had time to do further testing on this...maybe this weekend...

Iain
jpsa
Offline

Member

Posts: 65
Threads: 9
Joined: May 2011
#38
2013-04-10, 08:29 AM
Zeb Wrote:@jpsa: Same question with respect to your upgrade to Windows 7: Did you update Windows 7 first or install Patch 2 first? Granted, this very likely has nothing to do with the problem.
I performed a clean installation of Windows 7 together with all online updates, around September last year. I then installed the then current NPVR, together with the current patches rollup, and AFAIR this problem was immediately apparent (but not annoying enough for me to do anything about it!)
stustunz
Offline

Posting Freak

Posts: 5,111
Threads: 112
Joined: Oct 2006
#39
2013-04-10, 08:34 AM
Yeah Microsoft has f@&$ed the firewall and admin rights
[SIZE="1"]Specs[/SIZE]
[SIZE="1"]Server:Cpu-Intel i3,ATI Radeon HD 5670 ,OS-Windows 7,2gig ram. 2xHvr4400,Nova-s plus(dvb-s SD),hvr2210(dvb-t HD)[/SIZE]
[SIZE="1"]Client:Cpu-AMD am2,Gpu-Ati HD2100 integrated ,OS-Windows 7,2gig ram[/SIZE]
[SIZE="1"]Client:Cpu Intel 2 gig ram ,Nvidia 9400[/SIZE]
[SIZE="1"]ClientTongueopcorn Hour A110[/SIZE]
[SIZE="1"]Client:Samsung [NZ][DVB-s][2012]BD-E5900x2 [/SIZE]
[SIZE="1"]Client:Samsung [NZ][DVB-s][2013]BD-F6500 [/SIZE]
jpsa
Offline

Member

Posts: 65
Threads: 9
Joined: May 2011
#40
2013-10-02, 09:33 AM
I have a bit more information: disabling IPV6 on the client via

Control Panel -> Network and Internet -> Network and Sharing Center
Local Area Connection -> Properties

seems to cure the slow startup for me. I've actually disabled it on both client and server, but I think it was the client which made the difference. If anyone else suffering from this problem doesn't need IPV6, this could be a suitable workround for them.

Unfortunately I still don't know *why* disabling IPV6 helps... Sad
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (5): « Previous 1 2 3 4 5 Next »


Possibly Related Threads…
Thread Author Replies Views Last Post
  All my recordings start 90 sec early ncsercs 2 1,438 2022-03-19, 03:28 AM
Last Post: sub
  Nextpvr GUI and Service will not start bigbigblue 3 1,952 2020-02-18, 01:53 PM
Last Post: bigbigblue
  Start With Remote RTKAT 2 1,468 2020-02-13, 03:59 PM
Last Post: RTKAT
  No video or audio from start of playback smiffypr 8 3,758 2020-02-05, 05:11 PM
Last Post: smiffypr
  Unable to start device Device failed to start cazz 6 2,963 2019-04-29, 07:32 PM
Last Post: cazz
  Black screen at start of play - sometimes Petrovski 7 2,318 2019-03-22, 06:34 PM
Last Post: pBS
  Digital Devices Cine S2 - 'Failed to start device: 0x80004005' solidservo 14 5,741 2019-02-28, 08:59 PM
Last Post: easy74
  Run custom .bat file at start and end of recording bm_00 17 4,645 2019-01-20, 09:29 PM
Last Post: sub
  Slow to start playback nightsbird 8 2,416 2019-01-17, 02:39 AM
Last Post: nightsbird
  Multiple Clients one NPVR Server Coulen 2 1,640 2019-01-10, 06:29 PM
Last Post: sub

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode