Persistent Bi-Di VPN problems

Using connections via Registered Domain Names into Hardware routers that
forward correctly to RRAS servers on their respective private networks. That
works as I can do regular old VPN just fine!!!

My setup is two domains, HOME & WORK.

After configuring Bi-Di persistent VPN. . .
On a DHCP host from Home, I can ping any WORK DHCP or STATIC host by name
and IP. Woo-hoo!!!
ping from STATIC IP WORK host (not the RRAS machine) to HOME DHCP/STATIC
host works but only by IP address. But with the -a option, it does return the
host name. hmmm?!?!
On a DHCP host from WORK, I can ping only HOME DHCP/STATIC host by IP, and
the -a option does NOT return the host name, just the ip address.

Any ideas???

Again, home to work is just fine. . . work to home has a few glitches.

Here's the set-up (Arrived through by trial and error as this is all so new
to me):
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

HOME NETWORK:
IP 192.168.2.0
MASK 255.255.255.0
HW Router 192.168.2.1
ADs (2003) DC 192.168.2.101
RRAS(2003) LAN NIC 192.168.2.101
RRAS(2003) LAN NIC Gateway 192.168.2.1
RRAS(2003) WAN NIC 192.168.2.102
DNS Server 192.168.2.101
WINS Server 192.168.2.101
DHCP Server 192.168.2.101

HOME DHCP Options:
Router 192.168.2.101
Name Servers 192.168.2.101
DNS Servers 192.168.2.101
Time Servers 192.168.2.101

HOME DNS Options:
DNS Fowarders (ISP IP addresses)
192.168.0.96

HOME RRAS Options:
Demand Dial I/F WORK_ROUTER
STATIC ROUTE 192.168.0.0 / 255.255.255.0
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

WORK NETWORK:
IP 192.168.0.0
MASK 255.255.255.0
HW Router 192.168.0.1
ADs (2000) DC 192.168.0.96
RRAS(2003) LAN NIC 192.168.0.99
RRAS(2003) LAN NIC Gateway 192.168.0.1
RRAS(2003) WAN NIC 192.168.0.97
DNS Server 192.168.0.96
WINS Server 192.168.0.96
DHCP Server 192.168.0.96

WORK DHCP Options:
Router 192.168.0.99
Name Servers 192.168.0.96
DNS Servers 192.168.0.96
Time Servers 192.168.0.96

WORK DNS Options:
DNS Fowarders (ISP IP addresses)
192.168.2.101

WORK RRAS Options:
Demand Dial I/F HOME_ROUTER
STATIC ROUTE 192.168.2.0 / 255.255.255.0
.

Relevant Pages

  • Re: Working on howl port
    ... software needs to work as if it has no control over network allocation, ... the host does not have knowledge of what IPv4 Link- ... these modifications reduce the reliability of the DHCP service. ... is not sufficient reason to unconfigure a valid DHCP ...
    (freebsd-net)
  • Re: DNS, DHCP and classes
    ... I can't help with the DNS and DHCP changes, but I do want to clarify what you're doing so that someone else may be able to help on where your problem may lie. ... DHCP is set up to recognise all three networks and ignore requests from the 10/24 network. ... All bits set on a host address is a broadcast address for that network. ...
    (uk.comp.os.linux)
  • CERT Advisory CA-2002-12 Format String Vulnerability in ISC DHCPD
    ... The Internet Software Consortium provides a Dynamic Host ... have not seen active scanning or exploitation of this vulnerability. ... NSUPDATE allows the DHCP ... significant impact on your normal network operations. ...
    (Cert)
  • CERT Advisory CA-2002-12 Format String Vulnerability in ISC DHCPD
    ... The Internet Software Consortium provides a Dynamic Host ... have not seen active scanning or exploitation of this vulnerability. ... NSUPDATE allows the DHCP ... significant impact on your normal network operations. ...
    (Cert)
  • Re: DNS, DHCP and classes
    ... I can't help with the DNS and DHCP changes, but I do want to clarify what you're doing so that someone else may be able to help on where your problem may lie. ... DHCP is set up to recognise all three networks and ignore requests from the 10/24 network. ... All bits set on a host address is a broadcast address for that network. ...
    (uk.comp.os.linux)