VPN Picking up the wrong IP Address

I created a new DHCP scope to replace an old one. I needed more IPs so I just changed the subnet mask, nothing else.

Everything seems to be working fine except VPN. We're able to connect to the VPN but then get the error message.

Remote Desktop can't find the computer "<computer>". This might mean that "<computer>" does not belong to the specific network.  Verify the computer name and domain that you are trying to connect to.

I noticed that the IP address that the "Routing and Remote Access" dishes out is not within our IP address scope. It's 168.xxxxxxx. I think it gets these when it can't find the DNS server.
Obviously there's something i need to change because of the change in subnet mask.
ronfastI.T. DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RaithZCommented:
That is near the range that gets when an IP address can't be obtained, often called the auto-configure address.  Are you sure its actually handing out addresses?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Fred MarshallPrincipalCommented:
What is the subnet mask in the VPN setup?  Did you change that also - to match the new subnet?
0
ronfastI.T. DirectorAuthor Commented:
I just changed to subnet of the VPN setup to match the new subnet on my domain controller. still didn't work

I'm new to Routing and Remote access. it must not be handing out IPs because i checked the person that's connected to the VPN and it shows the 169.xxx
I'm not sure why it's not handing out IPs
0
ronfastI.T. DirectorAuthor Commented:
I disabled R and RA and then recreated it and it seems to have solved the problem. the IPs that it's handing out are in the correct range. Not sure why that corrected the problem. Any ideas? I hate not knowing why solutions worked

Glad it's working though.
0
RaithZCommented:
At this point I can only guess as to the cause but it may have been that the R and RA needed to be restarted to get the new configuration.  As to why it stopped working when you changed the configuration I do not know.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.