Re: VPN Error 733, Event Log Error 20050 with SBS 2003

Nick Marks wrote:
Thanks for getting back to me Joe

I've run through your suggestions; I checked in RRAS ports and I've got
all 5 miniports, so no problem there, however, when I look in my DHCP
leases can only see the LAN clients. I assume I have no entries for RAS
because no VPN clients have ever got as far as being assigned an
address. Also, I'm trying to assign client addresses from a static pool
outside the DHCP range (my pool is from x.x.x.40-49 and my DHCP range
is x.x.x.50-254)

I don't think there's any need to do that, but it shouldn't do any harm
either.

I've also looked at your pointers for enabling all authentication
methods. As suggested I've enabled all authentication and encryption
methods on both the server and client. Still no cigar, same error
messages

For the record, I'm sure the problem isnt with routing; I cant
establich a PPTP connection when I'm on the same LAN as the server.
Also, when I tested with pptpsvr/pptpclnt the server received the
message from the client (but the client never received a message back
from the server)

Any other ideas?



On the basis that there is one server and multiple clients, we can
probably assume the server is at fault. Have you looked after this
server from installation, or could there have been configurations made
you don't know about? Certainly PPTP should work out-of-the-box from a
LAN machine after the appropriate selections are made in the Remote
Access and CEIC wizards. But there's an enormous number of ways to
stop it happening, if someone else has been playing around.

I can't recall if RRAS is one of those bits of Windows that's easy to
reinstall, but if so, I think I'd try that next. The PPP negotiation
isn't working, and you've eliminated the common causes. I think I'd
want to start again with a known clean RRAS, and I would assume that
if reinstallation is practical, that would happen.

It's also possible that after the weekend one of the Microsoft people
will come back with a rigorous sequence of checks. I've just picked
things up as I've gone along. I don't have any flow diagrams for the
system, or documentation on the log files. If you've enabled 'tracing',
by the way, there are *lots* of log files in the directory of that name.
.

Relevant Pages

  • Re: Remote Access Wizard fails to complete with error in rraslog f
    ... Windows Server 2003 SP2 is also now on the server which was ... Reading VPN Server Name returned OK ... Checking whether RRAS is already running returned OK ... Enabling DHCP client addressing returned OK ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not communicate with other hosts on network
    ... Micro Office Scan client can cause this issue. ... Posting the both client and server routing tables may help. ... Clients can connect to our RRAS server through both PPTP/L2TP and dial-up ... connections and they will be authenticated on the network with no errors. ...
    (microsoft.public.win2000.ras_routing)
  • Network Admin-Myrtle Beach, SC
    ... SofTec I.T. has a terrific permanent opportunity with a premier client ... for a Senior Network Administrator. ... Configures and maintains the organizations LAN server and LAN ...
    (comp.dcom.sys.cisco)
  • Re: Cant browse the network over VPN?!
    ... running WINS on the LAN, WINS will have an entry for the Domain Master ... If the client has the correct WINS address, ... > server, and you attempt to connect to a computer using a PPTP/VPN client, ... > opening Network Knighthood. ...
    (microsoft.public.windows.server.networking)
  • XP VPN - Force nslookup to use DNS servers supplied by RRAS?
    ... client connecting to office LAN via Windows VPN connection, ... the client will attempt to connect to a server on the LAN by ... who frequently use the Windows VPN connection to ...
    (microsoft.public.windowsxp.work_remotely)
Loading