Re: Help! RRAS on SBS2003

Tech-Archive recommends: Speed Up your PC by fixing your registry



First up, the internal interface not having an IP address is a symptom,
not a cause. It does not get an IP address until the first remote client
connects. It doesn't need one until that happens.

Can you connect from a local machine using the server's local IP
address? This is a good way to check the server config. If that works, you
can start checking why it doesn't work from the outside.


Alexis wrote:
> I have a SBS2003 Std (patched) with one NIC which I am trying to set
> up as a VPN server. On another SBS2003 Std (patched), I followed the
> instructions, set it up as remote access and VPN demand-dial,
> configured 5 PPTP ports, set up a bank of static IP's. I did all
> this after running the Remote Access Wizard. It works fine.
>
> This time, when I disabled and reenabled RRAS, when I selected option
> 1 (VPN and remote access), I got a warning about only 1 NIC and that
> I need to do a custom configuration. I did a custom configuration
> selecting VPN and demand-dial. I configured the ports and static
> IP's. This time I cannot connect. RRAS is running. As I'm looking
> at RRAS status, the first thing I notice is that under IP Routing,
> General, the Internal interface does not have an IP address assigned
> and status is Non-operational. Under Network Interfaces, however, it
> shows as Enabled. When I do ipconfig, the working server shows the
> PPP adapter and the local connection, the problem server shows only
> the local connection.
>
> I've tried various combinations of settings and searching the kb,
> nothing talks about this issue. I have been able to connect to this
> box before, but was having problems with authenticating which is why
> I disabled/reenabled RRAS.
>
> I have an identical setup running with the first box. Both rely on an
> external router (same brand/model) for DHCP. The only difference is
> that the first box is a Gateway and the second is HP. Another
> strange thing - as I was checking the state of the RRAS service on
> both servers, I noticed that the description of RRAS (on top left,
> where the hyperlinks for stop/start/restart are) was different on the
> Gateway (verbose) vs. on the HP (brief). I patched the GW with SP1,
> and bought the HP with SP1 installed (supposedly). MS Update shows
> both being patched, but it seems like the two machines are running
> different versions of RRAS.
>
> Hopefully someone on this list can help - I appreciate it.


.



Relevant Pages

  • Re: Passing custom exceptions server to client
    ... straight-forward.This definition exists in a common assembly; the server ... code throws an exception of this type and that works (is displayed ... then False is returned; passing False (remote) as ... the element of the application configuration file or set ...
    (microsoft.public.dotnet.languages.csharp)
  • Problem joining Windows domain from remote VPN/PPTP box
    ... server OK with administrator rights (configured via Routing and Remote ... On client there exists static route for remote network that points to ... following information can help you troubleshoot your DNS configuration. ...
    (microsoft.public.windows.server.active_directory)
  • Re: VPN Error 733, Event Log Error 20050 with SBS 2003 - revisited
    ... the VPN from within the LAN with anti-virus ... It seems that I need to look at repairing the whole of RRAS. ... disable or uninstall any antivirus software on the RRAS Server. ... check if there are some firewall between remote VPN client and RRAS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2004 & SBS 2003
    ... NAT is configured through RRAS. ... This is what is making me think that it may be a configuration ... I decided to take your advice and reinstall the server ... tools hoping that reconfiguring with the wizards would correct whatever was ...
    (microsoft.public.windows.server.sbs)
  • Re: RRAS and RDP issue
    ... While the VPN configuration was not the issue, ... > look into the basic firewall setting in RRAS. ... > expand the server tree ) then expand the IP Routing ...
    (microsoft.public.windows.server.sbs)