|
General Discussion General discussion about SageTV and related companies, products, and technologies. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
Can't access Sagetv web site-Modem reboot fixed it
Help For some reason I can't access the Sagetv.com web site from either of my laptops at home. I have Verizon DSL and I keep getting the message "connection refused". I turned off the firewalls and tried turning off the security settings but no luck. I have no trouble connecting at work, not sure who our ISP is. Any help would be appreciated
Thanks Jerry Last edited by Jblk9695; 07-22-2005 at 09:59 PM. Reason: Fixed the problem |
#2
|
|||
|
|||
#3
|
||||
|
||||
Thanks Rich, still no success. I get the "Cannot find server or DNS Error
Internet Explorer " message. I even tried the new Firefox browser with no success, I think it has to be a problem with Verizon. I'll try and call tech support tomorrow and see what they can come up with. If you have any other suggestions I'll be happy to try them, thanks. Jerry |
#4
|
||||
|
||||
Update- I unplugged the DSL modem and the Linksys wireless router for about 15 mins., plugged everything back in a walla I have Sagetv.com. Must have been one of those cyberspace gremlins Anyway, it's fixed and I'm a happy camper
|
#5
|
||||
|
||||
Quote:
__________________
HTPC HW: Gigabyte GA-EP45-UD3P, Intel Q9400, 2GB Corsair RAM, PNY Nvidia GT210 vid card, 3 HVR2250s, 2 PVR250s, USB-UIRT (2 STBs), Internal FireWire/Dual IDE Converter (IFC-1) HTPC SW: XP Pro/SP 2, SageTV v7.1.5.252 Beta, Java v1.6.0_10, PVR drivers v1.18.21.23257, HVR drivers 7.6.1.27118 HD100 Extender: 2 (server is just a server) Future plans: 1 more HVR2250, 1 Ceton CC 4-way tuner, 10TB diskspace Issues: 1 PVR250 not working, system board? |
#6
|
|||
|
|||
So where are you accessing it from? :P And yes, most consumer Inet gateways (aka routers -- no that they actually route) act as DNS forwarders and the setting is transmitted via DHCP.
Go to a command prompt and type this --> nslookup sage.tv It should kick back 68.106.89.96 |
#7
|
||||
|
||||
coulda been a fuxed up arp cache in the linksys too... but hey... glad to see you got it working.
|
#8
|
||||
|
||||
Sometimes "ipconfig /flushdns" at the command prompt will help too. Has for me before...
|
#9
|
||||
|
||||
Thanks for all the replys, I'll keep the suggestions on file for the next time this happens
Jerry |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|