10-04-2008 11:18 AM
When I try to assign a name for my LinkStation Pro Duo in Web Access, and set Web Access Service, I get error: "Error accessing BuffaloNas.com, check internet settings."
My Internet is accessable, my router have UPnP enabled, I disabled Windows' firewall, disabled virus proterction software... Did the same from Windows XP Pro, Windows Vista Business... Still not getting through. No clue what this means. Could it be that registration service does not work over the weekend? I can access BuffaloNas.com via web browser.
Can someone help? Please...
11-08-2008 06:26 AM - edited 11-08-2008 06:26 AM
11-12-2008 09:58 AM
In your router you need to have port 9000 tcp/udp forwarded to the IP address of the Buffalo NAS.
as far as the DNS settings if you don't know what yours is you can put in the IP of your router.
02-10-2009 09:12 PM
I had to change my router and everything works even FTP, but I can't use the BuffaloNAS.com site anymore to share files.
I messed around with the settings and disabled UPnP. Now I can't enable it, so I forwarded the port 9000 manually. Hopefully my FTP still works.
Is there anything I need to do to be able to use the BuffaloNAS.com again? Does it have anything to do with the BuffaloNAS.com name or key?
12-09-2009 11:02 AM
I'm looking for help with a very unusual problem.
I have a Linkstation duo setup at the office as an FTP and have a 'Pin Hole" setup to the ip address.
It has worked fine for months and still does for everybody except the guy that set it up, me!
Working from home:
I use the Buffalonas.com for access. I enter my id and pw and the page begins to load, I see what appears to be a error flash and then it shows 'Done" What shows is the page with the bars at the top and the bottom and the Linkstation logo. No folders, just a white page.
My efforts to find the cause have been as follows:
Four different computers using xp, win7 ie7 and ie8.
Clean install of xp with no antivirus.
Two different dsl modems and routers
One dsl modem with no routers
Buffalo support has logged on twice with no problems.
So, has anyone experienced this type problem, or does anyone have any theory as to what to check next?