2006-07-19, 10:58 PM
Hi,
I have the websceduling is running on the default port and I have pinholed my router to forward requests on ports 7647 and 80 to port 7647 on the PVR. I use dyndns to assign a static domain to my router (it has builtin support for updating dyndns records). I had to add port 80 as a second port because the IT department at my partner's work had port 7647 blocked.
I can use the webscheduling fine from my work and other machines on the LAN, but my partner cannot from her workplace - she gets the login page, but when she clicks 'Log In' after entering the username/password, "The little bar thing goes along at the bottom but the screen doesn't change" (her words ). Any idea why she can't login but I can?
PS: The webscheduling feature is awesome! I didn't even know about it until someone at my work started using GBPVR and told me about it :eek:
I have the websceduling is running on the default port and I have pinholed my router to forward requests on ports 7647 and 80 to port 7647 on the PVR. I use dyndns to assign a static domain to my router (it has builtin support for updating dyndns records). I had to add port 80 as a second port because the IT department at my partner's work had port 7647 blocked.
I can use the webscheduling fine from my work and other machines on the LAN, but my partner cannot from her workplace - she gets the login page, but when she clicks 'Log In' after entering the username/password, "The little bar thing goes along at the bottom but the screen doesn't change" (her words ). Any idea why she can't login but I can?
PS: The webscheduling feature is awesome! I didn't even know about it until someone at my work started using GBPVR and told me about it :eek: