how to get VPN client to be able to see msWindows LAN

[stfaprc]

The LAN is not running AD (the PDC and BDC are running NT) and there is not yet a functioning LDAP. BIND 9.2 is providing the address->names on a RH9 box.

The VPN server is PoPToP version 1.3.0 and PPPd version 2.4.3
running on a Fedora Core 4 box
CHAP authentication is on
server connection is 192.168.1.250,
address allocations are 192.168.1.251-253
LAN is the full 192.168.1

Using XP, people are able to make a VPN connection and they can see the LAN's ip addresses, ie: their softphone can connect to our VoIP box on 192.168.1.200
But they can not see any of the LAN names or even the Network Neighborhood.
How can I set this up so that users can make the VPN connection and then be able to successfully do a
"net use \\LANDomain\PCName\Drive\ " ?

thanks,

 

[burtsbees]

address allocations are 192.168.1.251-253"---are these for the vpn connections? If so, they are in the same subnet as the LAN. This can only work if you exclude these addresses from being NATted---then they will be able to see the LAN.

Burt

 

[stfaprc]

Yes, "address allocations are 192.168.1.251-253" are for the vpn connections only.

I do not understand what you mean by:

exclude these addresses from being NATted

As far as I am aware, the addresses are not being NATted.

The vpn clients CAN see 192.168.1.200, without any issues. What they can not see are the "names" on the msWin LAN.

I'm not so sure if they can see the names from the DNS server either, I'll have to check on that.

 

[burtsbees]

So the rest of the LAN is being NATted, and the vpn addresses are not?

Burt

 

[stfaprc]

where is the NATting coming into this?
There is no NATting that I know of.

 

[burtsbees]

How does the rest of the LAN get out to the internet? If they do, then those addresses are being NATted somewhere, unless you're on a Metro-E...

Burt

 

[stfaprc]

oh, the LAN pc's get out through a WatchGuard firewall.

The DNS is setup for internal / external access, but the LAN names that are in the internal zone are not mentioned at all in the external zone.

 

[burtsbees]

The the watchguard is doing the NAT. You need to exclude the vpn addresses from the NAT pool...

Burt