NMT not getting NPVR

[pcostanza]

The boss lady told me that since it's a nice day, I must leave my man cave for a while. When I get back, I'm going to remove all NPVR related items from the firewall and add them again from scratch. I think there's a conflict there from my reimaging.

I've rebooted umpteen times and I'll check the virtual store to be sure the shelves are clean.

Now to make the boss happy.

[pcostanza]

Martin, for the majority of the time, I do have this working. Sometimes I do have the same problem but I'm getting it to work more than not now.
I went and gave my system a static IP and did some tweaking on the router and that appears to be it though I hadn't made any changes previously.
What is the port I want to have open on the router? Are there more than 1?

Thanks for your patience and help. I definitely should win a prize for having the freakiest system though I do lots of beta testing so I deserve what I get.

[mvallevand]

You would definitely get better consistency related to master browser issues if you replaced the URL (not the Share Name) of

MEGAPC:mvpmc
smb://MEGAPC/mvpmc

with the static ip,

smb://192.168.1.112/mvpmc

If you want to do this, plugging in a spare USB keyboard into the PCH makes life easier.

Martin

[pcostanza]

What a great idea. One that I think I'll give a try.
Thanks again.

[pcostanza]

Worked perfect. Of course I never thought of using a keyboard....duh!

Now, how do I remove the GBPVR choice from the NMT? It's the first one listed and I since I no longer have it installed, I'd like to remove the link to it.

[mvallevand]

http://forums.nextpvr.com/showthread.php...post403711

Martin

[TomH]

You would definitely get better consistency related to master browser issues if you replaced the URL (not the Share Name) of

MEGAPC:mvpmc
smb://MEGAPC/mvpmc

with the static ip,

smb://192.168.1.112/mvpmc

If you want to do this, plugging in a spare USB keyboard into the PCH makes life easier.

Martin

Martin, (sorry if I'm sidetracking this thread , Paul)

Dunno if you remember my M34A "Unable to resolve host name" errors which led to immediate Win7 BSOD's...

Your hint to Paul about entering the IP directly into the NMT URL field caught my eye.

So will ask if you would guess that using IP instead of share-name might lessen the "...unable to resolve..." errors ?

[mvallevand]

@TomH, it would not help with anything related to a BSOD, but it could help in the stability of establishing the initial connection if there are any delays in finding a master browser to resolved the machine name.

Martin

[TomH]

@TomH, it would not help with anything related to a BSOD, but it could help in the stability of establishing the initial connection if there are any delays in finding a master browser to resolved the machine name.
Martin

Martin,

Bad news so far with using IP in the NMT shares URL... though most of nPVR seemed to function okay, the Universe/Playon aspect got seriously broken.

Here's the sequence of events

FIrst, when substituting IP for share-name in the NMT Setup Shares menu...

* Initially Playon was found by Universe, but only empty folders presented.
* Found that pLAYoN was killed, and would not restart and hold
* Found that MediaMall service had stopped
* Manual restart of the service and restart of PlayOn
* They would not stay on/running when nPVR/Universe/PlayOn was selected

Now the bad news...
Secondly, I reverted back to 'share-name' in the NMT Setup Share URL menu... and restarted the PC

Now, immediately upon selecting PlayOn in the Universe menu the MediaMall service is stopped as before. All the same symptoms as above when the IP was being used in NMT share URL

EDIT2 -- actually I see now that the MediaMall servcie is stopped immediately whan Universe is selected on the Main Menu


How do I help you figure this out?

Attached is the npvr log.

On my knees, praying and secretly hoping that there's something cached somewhere

Thanks,

EDIT to add attachement

[mvallevand]

Any IP settings on the NMT would not impact Universe at all until you try and play a file, since the plugin is actually running on your PC connecting PC to PC. I suggest installing the latest PlayOn update, and then try again from the PC and copy the logs in the Universe support forum

Martin