two monkeys and a vpn

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Two monkeys have escaped from a zoo and have attempted to create a VPN between a client running Windows XP and a "Server" running windows 2000 Professional
They've managed to establish the connection by running the VPN wizard on both machines
The VPN is present in Network Connections on the server pc
Both PC's obtained 169 ip address
No shared files were available to the client
No computers were showing up in Network Places on the "server "pc (w2kpro
How do they make the files on the server accessible/visible to the VPN client (xp)
Any ideas welcome as they're going bananas!!
 
Are you able to ping the server from the vpn client? What happens when you
try net use to the shared directory on the server?

Thanks,
Sharoon

169 said:
Two monkeys have escaped from a zoo and have attempted to create a VPN
Click to expand...
between a client running Windows XP and a "Server" running windows 2000
Professional.
 
yes all connections are fine

problem solved

typing the name of the server into internet explorer brought up all shared files....ooo oo

cheers
 
This sounds like the problem you get if you set up a Windows VPN on a server
with only 1 interface, or on a multihomed domain controller.
(Browsemaster conflicts between the interfaces)
 
No, ICS won't give you those. They are APIPA addresses. They are handed
out when the machine is set to get IP addresses from DHCP, but no DHCP
server can be found.

The VPN server should lease IPs from DHCP, then hand these out to its
clients as required. If you can't see why your VPN server is not getting IP
addresses from DHCP for this, set it to use a static pool.

169 said:
can anyone tell me why my vpn clients pick up 169 rather than 192.....is
Click to expand...
ICS the problem because my networked pc's lose internet connection when vpn
is established?
 
I understand what APIPA is, hence my user name
What I'm confused about is if ICS provides DHCP,NAT and DNS services to my client machines in house why does a vpn client not get a 192.168.y.z address
 
As I said earlier, a VPN client gets its IP address from the VPN server,
not directly from DHCP or an ICS allocator. So the question is really why
can't the VPN server get IP addresses from DHCP/ICS. If it is set to get
these addresses automatically but cannot find an allocator, it will use
APIPA.

169 said:
I understand what APIPA is, hence my user name.
What I'm confused about is if ICS provides DHCP,NAT and DNS services to my
Click to expand...
client machines in house why does a vpn client not get a 192.168.y.z
address?
 
Back
Top