Win 2K3 RAS VPN Server - Won't Relay to DHCP

Go an issue with my RAS VPN on Win2k3:
Just switched servers that's running this service.  New server does not seem to be relaying DHCP to DHCP server.  When I look at the DHCP server's scope, we do not see the entries for the RAS.  On the old server (also a 2k3) it would put entries on the DHCP server scope.  I have DHCP Relay setup in the RAS, using both internal and the NIC.  Can't connect to the VPN, get a 733 error
Any Suggestions?
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.

Error 733 suggests to me its not a DHCP problem. It would still connect, but would fail to assign an IP address. make sure your router is correctly pointing to the new server
JamesonJendreasAuthor Commented:
It defiantly is pointing to the correct place.  We get the 733 while trying to register the computer onto the network - The connection verifies user name so the connection is being made.  Number one reason why I feel it's DHCP is because the RAS server is not putting RAS entries into the DHCP scope.

From a VPN trouble shooting website:
 "Analysis: normally, a VPN client receives TCP/IP CP reported error 733 because of the TCP/IP settings. In the most cases, the VPN client does not receive a IP from the DHCP.. "
Is there a reason why you are having the RAS server add to the scope on the DCHP server? I would suggest having the DHCP server predefined and have the RAS server relay DHCP requests to the DHCP server.
JamesonJendreasAuthor Commented:
It's not adding to the scope - When we Relay to the DHCP there should be entries on the DHCP scope that are assigned to RAS, and takes up IP's from within the pre-defined scope.
JamesonJendreasAuthor Commented:
Found the issue - Forgot to check "Allow IP-Based remote access and Demand Dial-in Connections" in the general properties

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
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 2003

From novice to tech pro — start learning today.