Archived from groups: comp.security.firewalls (
More info?)
"Leythos" <void@nowhere.com> wrote in message
news:MPG.1af2c84ab453384698a41b@news-server.columbus.rr.com...
> In article <fE5ic.39$yd1.23@newsfe1-win>, nospam@nospam.com says...
> > The reason I ask the question is because I have had nothing but
aggravation
> > with their products. I just wanted to see if it was just me, or maybe I
just
> > expect to much. Here are a few examples:
> >
> > The documentation they provide on how to set up DI-804HV and their
DSL-300
> > together is technically inaccurate and therefore resulted in several
calls
> > to support. The document has still not been changed although the problem
was
> > eventually acknowledged after some eventually took the time to check
what I
> > was talking about.
> >
> > I have reported a bug in the DI-804HV to tech support both verbally and
in
> > writing that they have acknowledged, yet done nothing about after
several
> > weeks.
> >
> > I was told prior to buying the DI-804HV that I could tunnel through it
using
> > IPSEC whilst connecting to the LAN behind it using the built in winXP
vpn
> > client. After buying four of these boxes for various clients, it turns
out
> > this simply is not true, it doesn't work. Support have apologised for
> > misinforming me...(four hundred quid and countless wasted hours later).
>
> It sounds like you could have other problems than the D-Link, can you
> describe the networks that you have configured and how things are setup.
> A basic NAT router will let you VPN out to another location without any
> problems, but you want both private subnets to be different - meaning
> that if your local is 192.168.0.x and the other one is 192.168.0.x you
> are going to have problems. If you were meaning that you can use your
> local resources while VPN'd into the remote location, then it's only an
> issue of setting the "Use default gateway" option on your side.
>
> It's a common mistake for people using these cheap routers to NOT put
> each one in it's own unique subnet that is different from their own
> local subnet.
Thanks for your post, but subnets were not an issue in this instance. The
problems were caused by extremely poor communication and documentation on
D-links part.
Paul