Re: WK2 VPN: temporary 169.254.x.x IP address being assigned.

Tech-Archive recommends: Fix windows errors by optimizing your registry

By default, the RRAS will assign 168.254.x.x to the VPN client if it can't connect to the DHCP. Posting the result of ipconfig /all may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Pedro Innecco" <pedro.innecco@xxxxxxxxxxxxxxxxxx> wrote in message news:2A3BA3BA-CBE5-4595-80DD-8439EB404FF6@xxxxxxxxxxxxxxxx
Hello there,

Hope someone can help me. I think my question might be rather easy (I must
be missing something!)

I am trying to set-up PPTP VPN for 5 clients in my organisation. I manage to
"dial-in" and connect to the network. Although it works and I can see the
server, the client is assigned with a temporary IP address of 169.254.x.x as
if there was no DHCP server in my network.

My network information:

Network: 192.168.100.x
Subnet: 255.255.255.0
Gateway: 192.168.100.254
DNS: 192.168.100.1 (the everything server)

Server is pretty much running everything: DC, DHCP, DNS, RAS, etc.

How I set-up RAS:

1. Started RAS
2. Right click server and chosen "Configure and Enable RAS"
3. Selected the Remote Access Server option (I followed the instructions at
http://neworder.box.sk/news/13395), selecting RAS will give me 5 VPN ports
with PPTP and 5 with L2TP.
4. I tried first to assign IPs using my DHCP server, and then I tried using
a pool from 192.168.100.101 to 192.168.100.105. Both options give me the
same result (that is, an IP of 169.254.x.x assigned).
5. I am not using RADIUS.

I also tried to add my Local Area Connection under DHCP Relay agent in RAS,
and I also tried to right-click the DHCP Relay Agent contained and add my
DHCP server IP address (192.168.100.1) to the list.

Still, I can't figure out how to have an IP address of 192.168.100.x
assigned to my VPN clients. At the moment the clients CAN ping/access the
192.168.100.1 server's IP address, but they can't see anything else on the
192.168.100.x subnet, and the connection to the internet drops on the client
when it dials-in as well.

Any ideas what I am doing wrong?

Thanks in advance for the help!

Regards,
Pedro

Relevant Pages

  • Re: My Server is not anymore seen on network plese help ?
    ... here is the client ipconfig. ... wich as adress 192.168.1.102 which it is not reachable for some reason ... As you can see the DHCP ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)
  • Re: Application Hang
    ... Back to DHCP, what about the client ipconfig without the DG ip address? ... When the old server crashed, it required a new motherboard and CPU. ... You should see at least,006 DNS servers, 003 Router. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: DHCP handles Naks one one vlan differently
    ... If the problem is on the network with the DHCP server, ... Frame 156 ... Your (client) IP address: 0.0.0.0 ...
    (comp.dcom.sys.cisco)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)