Enhanced Web Admin

[ShiningDragon]

I don't know if it means something, but I can't ping you on both adresses.
I have a dyndns-adres myself and I can ping myself perfectly on that.

Edit; wrt the firewall, you disabled the router firewall as well?

No, i only disabled the WinXP Firewall. I would never disable the Router Firewall, but this should't be a problem. Otherwise my other Apps couldn't work too (like FileZilla Server).

No, ping isn't possible, because i disabled the reaction of pings within the router. But you'll se within the commandshell, that you're connected to my pc (because you can see the actual IP adress).

[HtV]

But you'll se within the commandshell, that you're connected to my pc (because you can see the actual IP adress).

You're right. I'm sorry I give up, but I keep thinking it's something in your router, because it works ok on your lan.:confused:

[ShiningDragon]

You're right. I'm sorry I give up, but I keep thinking it's something in your router, because it works ok on your lan.:confused:

...mhm, two completely different Routers? Mhm..., if i am home tonight, i'll shut down any kind of protection of my router and test again.
I was thinking about a missing service of WinXP, perhaps i have to install the Webserver from XP? I really don't know this; if i'd knew this, i wouldn't ask for help...

But thanks for trying help me ;-)

[HtV]

.
I was thinking about a missing service of WinXP, perhaps i have to install the Webserver from XP?

The server works doesnt it? Otherwise it would not work on your lan.

[ShiningDragon]

The server works doesnt it? Otherwise it would not work on your lan.

My PC isn't within a LAN. I have only 4 PC's at work and one PC at home. I can access from my home PC with the localhost command. The same at work. But i can't connect from outside to EWA; the connections with FTP works without any problems at fullspeed.

[UncleJohnsBand]

Nope, doesn't fix it (you're excused )

The xml tages were <title lang="en">&quot;Hannibal&quot;</title> FYI.

So now I have to ask: has the recordings conflict behaviour changed? I just noticed that there was a recording already scheduled at the same time, but the old behaviour was to allow recording of both shows, with a yellow "conflict" flag appearing on the manage recordings page.

However this new behaviour just says it (scheduling) failed, and not that there was a conflict. Both recordings (old behaviour) would be good IMO, despite the conflict status, as this can be overidden by those those using priority recordings e.g.

I used to remember it (would this have anything to do with sub's (sticky thread) patch for not being able delete recordings, I sort of remember this started after that), but it may be completely un-related.

k.

I don't know.....I didn't change anything.....The EWA simply calls the record show API that is provided with GBPVR....all the conflict determiniation is done in the GBPVR API code......

The message you see displayed about it failing was added back in build 36.....prior to that no message was displayed at all in EWA should a recording not schedule.

The check (as I think I mentioned before) is a simple check:
All shows to record are sent through the scheduling API.
Then a list of all record shows is pulled via the API.
The list of shows that were selected to record is checked against the list of recorded shows returned from the API.
If a show is not found then it is listed at the top of the grid like you are seeing.

To my knowlege nothing has changed in the schedulerecording API that would prevent a show from scheduling in a conflict state....but only sub could answer that for sure.....

[UncleJohnsBand]

...mhm, two completely different Routers? Mhm..., if i am home tonight, i'll shut down any kind of protection of my router and test again.
I was thinking about a missing service of WinXP, perhaps i have to install the Webserver from XP? I really don't know this; if i'd knew this, i wouldn't ask for help...

But thanks for trying help me ;-)

Have you verified that the IP that is stored on dydns matches you WAN ip of your routers? I have (on occasion) see these get out of sync.....and it produces the results you are having....no ping avialble and get get to where you want to be becuase dydns is pointing to some IP that you had in the past....

[ShiningDragon]

Have you verified that the IP that is stored on dydns matches you WAN ip of your routers? I have (on occasion) see these get out of sync.....and it produces the results you are having....no ping avialble and get get to where you want to be becuase dydns is pointing to some IP that you had in the past....

Yep, i verified that. I tried EWA a few month ago too, but without success too.
But now i'll try to get it running...

[UncleJohnsBand]

Yep, i verified that. I tried EWA a few month ago too, but without success too.
But now i'll try to get it running...

Hmmm.....localhost:port/gbpvr/guide.aspx works on the local machine.......Correct?

Do you have a home network? Can you try http://pcnetworkname:port/gbpvr/guide.aspx and see if it comes up?

dydns.org:port/gbpvr/guide.aspx does not work......correct?

You have your port forwarded on your router to the host gbpvr machine (tcp....not udp)......Correct?

You have the port open on your firewall on the host machine or the firewall disabled alltogether.....Correct?

[ShiningDragon]

Hmmm.....localhost:port/gbpvr/guide.aspx works on the local machine.......Correct?

http://localhost:7647/gbpvr/guide.aspx <- YES, it works from the PC itself
localhost:7647/gbpvr/guide.aspx <- YES, it works from the PC itself <- NO, this DOESN'T work in the PC itself.

Do you have a home network?

Home: No, but at work. I'll try now.

Can you try http://pcnetworkname:port/gbpvr/guide.aspx and see if it comes up?

Mhm, just tested from another PC within LAN: Yes, this works fine.

dydns.org:port/gbpvr/guide.aspx does not work......correct?

Correct, this doesn't work on any PC in any direction from any point.

You have your port forwarded on your router to the host gbpvr machine (tcp....not udp)......Correct?

Yep, Port 7647 TCP forwarded to the GB-PVR Host.

You have the port open on your firewall on the host machine or the firewall disabled alltogether.....Correct?

Right, without this i couldn't access via http://pcnetworkname:7647/gbpvr on it; but http://tnb-theke.dyndns.org:7647/gbpvr doesn't work. Ip doesn't work too.

Any Idea?