INTERACT FORUM
More => Old Versions => Media Center 13 (Development Ended) => Topic started by: TheDuke on November 04, 2009, 04:52:49 pm
-
I have just upgraded from XP to Windows 7
Whenever I try to change to theatre view the program crashes
Have also downloaded and tried MC14 and the same thing happens
(By the way has the jriver site been down. Couldn't connect at home last night. Writing this from work)
-
The Theater View crash may be a video driver bug. Also visit Microsoft's DirectX site to see what you can find.
I don't think our web servers have been down recently.
-
Just wondering if the problem was that i couldn't access the J River server.
When the program intalls, if it needs to download some stuff, it may not have been able to, hence the probs.
will try re-installing tonight. Hopefully will work then
-
I don't think the crash is related to the server being unavailable. It's likely to be video related.
-
Working fine now.
After a lot of mucking around with my IP
For some reason the JRiver site was blocking my IP address 110.175.110.151
Can this get fixed please
After supplying a new temp static IP address I am not able to access the site
Have reintalled MC13 and all working fine
-
Could you please ask the JRiver site manager to look into this for me
i was talking to my ISP for ages last night, and it was determined for some reason
my IP address (listed in previous post) is being blocked by the JRiver site.
-
We aren't blocking specific IP's or any range that contains that address. Please do a tracert to whatever server of ours you are trying to reach and post the results here. Thanks...
-
Sure, will do.
How do I do a tracert?
-
google or Microsoft could probably help, but try this:
at a CMD prompt, type
tracert www.jrmediacenter.com
-
Still getting blocked on the way to the JRiver site. (writing this at work)
Here is the result of the tracert
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rob>tracert jrmediacenter.com
Tracing route to jrmediacenter.com [204.75.156.12]
over a maximum of 30 hops:
1 84 ms 81 ms 92 ms 192.168.0.1
2 154 ms 119 ms 231 ms adl-pow-kin-lns1-lo-20.tpgi.com.au [202.7.162.16
8]
3 117 ms 264 ms 208 ms adl-sot-way-crt1.tpgi.com.au [202.7.183.65]
4 169 ms 129 ms 219 ms 202.7.171.193
5 312 ms 323 ms 314 ms if-2-2.core3.SQN-SanJose.as6453.net [216.6.33.1]
6 326 ms 311 ms 328 ms Vlan55.icore1.SQN-SanJose.as6453.net [66.198.97.
10]
7 312 ms 330 ms 361 ms ix-2-0.icore1.SQN-SanJose.as6453.net [209.58.116
.14]
8 344 ms 312 ms 342 ms vlan89.csw3.SanJose1.Level3.net [4.68.18.190]
9 315 ms 402 ms 423 ms ae-82-82.ebr2.SanJose1.Level3.net [4.69.134.217]
10 320 ms 308 ms 309 ms ae-2.ebr2.LosAngeles1.Level3.net [4.69.132.14]
11 334 ms 335 ms 381 ms ae-4-4.car2.Phoenix1.Level3.net [4.69.133.37]
12 460 ms 392 ms 400 ms ae-11-11.car1.Phoenix1.Level3.net [4.69.133.33]
13 330 ms 391 ms 394 ms TELESPECTRA.car1.Phoenix1.Level3.net [4.53.104.3
0]
14 * 396 ms 495 ms 64-130-240-66.sparkplugbb.net [64.130.240.66]
15 378 ms 423 ms 344 ms ATR-6598.sparkplugbb.net [66.17.84.98]
16 * 485 ms 391 ms ATR-65102.sparkplugbb.net [66.17.84.102]
17 * * * Request timed out.
18 * * * Request timed out.
19 *
-
Bob may see something, but that looks normal to me. It's what I get from here.
Not all machines will respond.
You could try the same from work.
-
That traceroute looks fine.
What service exactly are you having trouble reaching? (for example, the forum, the main web page, the start page in MC, the download site, etc).
-
I am having trouble getting to any JR service main page, start page, forum, updates
I am just about ready to srcap my ISP and be done with it as they really should be sorting this for me.
This was their last email to me. I can't understand it at all. make any sense to you guys
Dear TPG Customer,
Thank you for writing to TPG Helpdesk.
We have used http://knossos.net.nz/checkdomain.cgi to check the site to avoid bias and lapses are found. Our servers strictly adhere to RFC standards reason why these lapses has an impact on these domains' accessibility via our network. Kindly refer bellow. Kindly contact the site administrator for possible rectification of the issue.
jrmediacenter.com
Name servers
The following name servers for jrmediacenter.com were found in the delegation from com:
jriver.jriver.com, IP address 216.14.188.108 (jriver.jriver.com)
ns2.jriver.net, IP address 204.75.156.8 (ns2.jriver.net)
Authority (SOA) data
Primary name server: jriver.jriver.com, IP address 216.14.188.108 (jriver.jriver.com)
Contact email address: hostmaster at [removed by JimH]
Serial number: 20355
Secondaries query every 10 minutes; retry every 5 minutes; expire after 7 days.
Time to live for negative responses: 10 minutes
Time to live of SOA record: 10 minutes
Other services
WWW server www.jrmediacenter.com found, IP address 204.75.156.12 (jrmediacenter.com).
The IP address for the name jrmediacenter.com is 204.75.156.12 (jrmediacenter.com).
--------------------------------------------------------------------------------
Additional information
indicates an error that can potentially cause access to services to fail.
indicates configuration that differs from convention, information that may improve operation or expands on other messages.
The list of name servers returned by the nameserver jriver.jriver.com at IP address 216.14.188.108 does not match those listed in the delegation for the domain in the registry for com. (This list is displayed under the ``Name servers'' section above.) Please check the registry data and ensure that it matches the data in the local name servers. The list obtained from jriver.jriver.com is as follows:
jriver.jriver.com, IP address 216.14.188.108 (jriver.jriver.com)
ns1.engen.com, IP address 204.75.156.129 (ns1.engen.com)
ns2.jriver.net, IP address 204.75.156.8 (ns2.jriver.net)
The NS list at ns2.jriver.net also does not match the list at the the registry for com, but does match the list at jriver.jriver.com.
A name server was found that is not listed in the delegation from com. This is:
ns1.engen.com, IP address 204.75.156.129 (ns1.engen.com)
The serial number for the SOA record (20355) is not in the conventional format. The common (but by no means compulsory) format for serial numbers is YYYYMMDDnn, where YYYYMMDD is the date of the last update, and nn is a sequence number for when there are multiple updates within a given day.
Some SOA timer parameters appear small. Recommended SOA record parameters for small zones, ie those containing just sufficient information to resolve mail and web services for a site, are:
Refresh: 86400 (one day)
Retry: 7200 (two hours)
Expire: 3600000 (1,000 hours)
Negative TTL: 3600 (one hour)
Operators of domains with more frequent updates may want to use smaller refresh and negative TTL values than the above.
Should you have any other issues, concerns, inquiries, or any other problem with regards to our product or service, please feel free to contact us at 1-300-360-855 or visit our Helpdesk website at http://www.tpg.com.au/helpdesk.
Kind regards,
Gust
-
Thanks for the feedback. There are no obvious issues but I'll clean up the extraneous nameserver and bump the timeouts. This may not happen until tomorrow.
-
Made the changes Monday night.
Any difference?