( 6 reviews )
-
Posted: Jul 27 2009
Most people looking at this router is probably looking for a router with VPN capabilities. IT JUST NEVER WORKED FOR ME. I bought this a year ago, and tried all I could to configure VPN. It never worked. I emailed them, and they would usually reply back to me after 2 or 3 days. And their answer is not even relevant to my problems, or I have already done what they wanted me to do. Or would ask questions, that the answers could be found in my email. I wouldnt mind waiting for 2,3 days for a reply, but I was hoping they would at least give me some clue as to what my problem was. I also called their customer support, I talked to them for about 40 minutes or so. (I dont think she did understand what VPN is) Then she finally gave up, and gave me another number to call. I havent called the other number yet, but I might give it a try. After all at this point there is really nothing to lose now.
-
Posted: Apr 22 2009
It is a wireless router and it is working on my small home network just fine.
-
( 1 of 1 found this review helpful ) Posted: Dec 18 2008
Despite all the negative talk on the web about this router I took a chance - primarily for one reason - It seems to be the ONLY router out there that supports Windows XP VPN client. (I had to return the Netgear vpn prosafe router because of this). - I already have a D-link router and it has been solid for years. DIR-330: The web interface seems solid to me. Here are the features/info I'm using. Firmware 1.12 (came on the router in the box) LAN 172.17.x.x with DHCP from 172.17.0.100..200 WiFi: WPA2-PSK/AES WAN fully automatic DHCP connection to AT&T DSL modem. Note:- I have had other D-link routers crash after a day until I found this out.... The AT&T DSL Modem hijacks 192.168.0.1 and screws up the routing tables if you have 192.168.0.x on the LAN side. SO - Don't use 192.168.0.x on the LAN side! (I was using 10.x.x.x until I installed this new router. The reason I changed from 10.x.x.x to 172.17.x.x was that when I VPN in there is a good chance that it'll be on a 192.168.0.x or 10.x.x.x network since these are so common. To make it so that I don't have the potential for any IP conflicts I chose a lesser used private network mask (from the 172.16.x.x...172.31.255.255 range). This allows me to keep static ip assignments in my WINDOWSsystem32driversetchosts file without worrying about DNS working etc. http://en.wikipedia.org/wiki/Private_network The VPN was configured so that the VPN server is 172.18.0.1 and the VPN DHCP range 172.18.0.100..200 The VPN is set up as L2TP/IPsec for the most security. I'm using the free Dynamic DNS from dlinkddns.com (built into the router) to track my DSL's real IP address and so far it's FANTASTIC!. I have a CNAME alias to it from my domain name serving at the (also free) everyDNS.net so that I can have "vpn.mydomain.com" instead of "blahblah.dlinkddns.com" I have not noticed any bandwidth drop from the older D-link router to this one. I can still watch streaming HD from Netflix on my TiVo-HD connected via WiFi. I'd give it 5 out of 5 but it's lacking a VPN wizard and it took me a little while to work out how to configure it. The docs on the right column of the web interface could be more featured too (in particular the ddns page). So.. I'd say give it a go.
