On Nov 4, 2009, at 1:13 PM, Matt Christy wrote:
On Nov 2, 2009 at 11:30:32, Dan Shoop Wrote:
---[snip!]---
And it also is good timing for kicking the network admin who
assigned
192.168.1.0/24 to the network you're servers are on in the first
place. Any netadmin with half a brain should realize that this
subnet
is too commonly used and would cause a collision with something one
day. It's like that knight in Indiana Jones would say as the guy
picked the wrong chalice and died, "he chose poorly."
-d
I actually dealt with this same issue when I took my position at my
current employer; the previous sys/net-admin had set up the LAN in
the
192.168.1.0/24 address range, and I couldn't get my Cisco VPN working
through the PIX. At first I thought my configuration was wrong,
and then
I realized my home network was configured exactly the same. Since I'm
the only one who needs VPN I just reconfigured my home network to use
10.1.1.0/24 instead (it works for me). Eventually I'd like to use a
private class b (172.16.0.0/16) here at the office to open up the
capability to all of my users. It's a project that's lower on the
priority list, but has to be done.
Anyway-- I liked your indy quote-- it made me smile.
Had a client yesterday who couldn't connect over VPN after
resetting their router. It was mostly because their default
settings were 192.168.1.0/8, just like the server they were trying
to connect to. I remembered what Shoop said the other day and
recommended said admin kicking.
