Re: RRAS Dial on demand
From: Andy (Andy_at_discussions.microsoft.com)
Date: 10/09/04
- Next message: Donnie: "LAN Problem"
- Previous message: WK: "RE:Trouble adding clients. "list of users/computers could not be foun"
- In reply to: Andy: "Re: RRAS Dial on demand"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 9 Oct 2004 09:41:10 -0700
Hold fire...
One of the servers I tested previously is now accepting connections.
I've made no changes whatsoever but the connection came up.
I thought I was confused before....
:-/
"Andy" wrote:
> I appreciate the help I'm getting on this and I've tried everything mentioned
> but I'm still suffering the same problem. Here's a run down of the settings.
>
> Server1: SBS 2003
> Created user DOD1 with dial-in access and member of mobile user group.
> Created DOD interface with name DOD1
>
> Server2: Server 2003 std
> Created user DOD2 with dial-in access.
> Created DOD interface with name DOD2
>
> Server1 can connect no problems to Server2
> IP routing works fine, both lans can see each other.
> Everything works as it should.
>
> Server2 cannot connect to Server1 because of the error first reported.
> "computer has exceeded its client access limit"
> I then stop the license logging service on Server1
> Server2 can now connect to Server1.
> IP routing works fine, both lans can see each other.
> Everything works as it should.
> SBCORE restarts the license logging service and the connection goes down.
>
> Server1 happily accepts VPN client connections but not DOD connections.
>
> I've gone through every conceivable setting time and time again.
> Wouldn't the fact that the connections work when the logging service is
> stopped suggest that the configuration, credentials and routing are all
> correct.
> The 2003 std server accepts DOD connections, SBS 2003 does not.
>
> I've also shown the problem to a couple of colleagues and they suffered the
> same issue attempting to connect to servers which they had set up.
> That's now 3 different people on a total of 6 different SBS 2003 installs
> all suffering from the same problem.
>
> Andy
>
>
>
> "David Copeland [MSFT]" wrote:
>
> > Andy,
> >
> > On my SBS 2003 server I was able to do the following
> >
> > Created a user named dod, set a password, and added the user to the Mobile
> > Users group (due to SBS 2003's RRAS dial-in permission policy)
> > Created a user named dod1, set a password, and added the user to the Mobile
> > Users group
> > Created a demand dial interface named dod, configured it to connect to the
> > SBS server's internal IP (only going to be used for testing), configured the
> > credentials for it to use as dod1 for the username, password
> > Created a demand dial interface named dod1, configured it to connect to the
> > SBS server's internal IP (only going to be used for testing), configured the
> > credentials for it to use as dod for the username, password
> >
> > I was able to then right click and select connect on either interface and it
> > was able to connect without the error you mentioned.
> >
> > Are you able to do the above on one of your servers?
> >
> > SBS's RRAS should not be limited in such a way to not be able to create a
> > demand dial connection.. SBS 2003 Std. Edition actually uses a demand dial
> > interface when configured in a dial-up configuration.
> >
> >
> > --
> >
> > Hope that helps,
> > David Copeland
> > Microsoft Small Business Server Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > Newsgroups:
> > SBS v4.x : microsoft.public.backoffice.smallbiz
> > SBS 2000: microsoft.public.backoffice.smallbiz2000
> > SBS 2003: microsoft.public.windows.server.sbs
> >
> >
> > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
> > news:uNvdhnZrEHA.3080@TK2MSFTNGP15.phx.gbl...
> > > Hi Andy,
> > >
> > > Can you post the ipconfig/all from the server please? How are you
> > > connecting
> > > to the internet? Do you also have a modem installed?
> > >
> > > --
> > > Regards,
> > >
> > > Marina
> > > Microsoft SBS-MVP
> > >
> > > "Andy" <Andy@discussions.microsoft.com> schreef in bericht
> > > news:B6A692F4-AEF3-41FF-94F1-A4079BD36ADA@microsoft.com...
> > >> On the server in question, there are 25 CALs installed.
> > >> The client is using maximum 12 at the moment.
> > >>
> > >> Remember, I'ved tried this on 3 other servers and they all suffer from
> > >> the
> > >> same fault. As soon as the license logging is stopped, they all work.
> > >>
> > >> Andy
> > >>
> > >> "Marina Roos [SBS-MVP]" wrote:
> > >>
> > >> > Hi Jaime,
> > >> >
> > >> > Well, you won't be able to keep that service stopped. How many CAL's do
> > > you
> > >> > have installed?
> > >> >
> > >> > --
> > >> > Regards,
> > >> >
> > >> > Marina
> > >> > Microsoft SBS-MVP
> > >> >
> > >> > "Jaime Brunicardi" <jbrunicardi@hotmail.com> schreef in bericht
> > >> > news:ef64a7fa.0410080044.357b3a4e@posting.google.com...
> > >> > > Hi Marina, Andy
> > >> > >
> > >> > > I have exactly the same problem and I agree with Andy it must be a
> > >> > > license bug because it works fine only by stopping the License
> > >> > > Logging
> > >> > > Service.
> > >> > >
> > >> > > Regards,
> > >> > >
> > >> > > "Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in
> > >> > message news:<emWabbMrEHA.3848@TK2MSFTNGP14.phx.gbl>...
> > >> > > > Hi Andy,
> > >> > > >
> > >> > > > What exactly is your problem? RRAS certainly is not crippled. Make
> > > sure
> > >> > that
> > >> > > > the vpn connection from the remote client is using the valid
> > >> > credentials,
> > >> > > > including the Windows domain. Are those remote clients joined to
> > >> > > > the
> > >> > domain?
> > >> > > > Did you check you have enough VPN ports configured? Default there
> > > are
> > >> > only
> > >> > > > 5.....
> > >> > > >
> > >> > > > --
> > >> > > > Regards,
> > >> > > >
> > >> > > > Marina
> > >> > > > Microsoft SBS-MVP
> > >> > > >
> > >> > > > "Andy" <Andy@discussions.microsoft.com> schreef in bericht
> > >> > > > news:D02A51E0-E32C-4C04-901C-2CD04F6AD0D0@microsoft.com...
> > >> > > > > I've done just that. I've also used the RRAS wizard and I've
> > >> > > > > tried
> > > the
> > >> > ISA
> > >> > > > > VPN wizard.
> > >> > > > > I've now tried it on three different SBS 2003 installations to
> > >> > > > > see
> > > if
> > >> > it
> > >> > > > was
> > >> > > > > just me or if there's something going on and it didn't work on
> > >> > > > > any
> > > of
> > >> > > > them.
> > >> > > > > I've set these DOD connections up for years, they've always been
> > > very
> > >> > > > > reliable and simple to do. I'm tearing my hair out.
> > >> > > > >
> > >> > > > > I'm convinced that Microsoft has crippled the RRAS in SBS 2003.
> > >> > > > > A SBS 2003 installation will not accept a dial on demand
> > > connection.
> > >> > > > >
> > >> > > > > BTW, turning off the license logging service makes it work
> > > perfectly.
> > >> > > > > This is not a configuration issue and given the fact that there
> > >> > certainly
> > >> > > > > isn't a license issue, I'm even more convinced that it's crippled
> > > (by
> > >> > > > design
> > >> > > > > as they say).
> > >> > > > >
> > >> > > > > :-(
> > >> > > > >
> > >> > > > > Andy
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > "David Copeland [MSFT]" wrote:
> > >> > > > >
> > >> > > > > > Andy,
> > >> > > > > >
> > >> > > > > > Try doing the following..
> > >> > > > > >
> > >> > > > > > 1) Create a user at both locations (SBS and remote server)
> > >> > > > > > named
> > > say
> > >> > dod
> > >> > > > > > and set a password for them and grant the dod user dial-in
> > >> > permissions
> > >> > > > > > 2) Then configure the credentials for each dial-on demand
> > > interface
> > >> > to
> > >> > > > > > authenticate as the dod user and password
> > >> > > > > >
> > >> > > > > > Do you still have the same problem?
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > >
> > >> > > > > > Hope that helps,
> > >> > > > > > David Copeland
> > >> > > > > > Microsoft Small Business Server Support
> > >> > > > > >
> > >> > > > > > This posting is provided "AS IS" with no warranties, and
> > >> > > > > > confers
> > > no
> > >> > > > rights.
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > SBS Newsgroups:
> > >> > > > > >
> > >> > > > > > SBS v4.x: microsoft.public.backoffice.smallbiz
> > >> > > > > > SBS 2000: microsoft.public.backoffice.smallbiz2000
> > >> > > > > > SBS 2003: microsoft.public.windows.server.sbs
> > >> > > > > >
> > >> > > > > > "Andy" <Andy@discussions.microsoft.com> wrote in message
> > >> > > > > > news:6C547FEE-71C6-47E1-B0CA-14421BB646F7@microsoft.com...
> > >> > > > > > > I've been trying to set up a Dial on demand routing
> > >> > > > > > > connection
> > >> > into
> > >> > > > SBS
> > >> > > > 2003
> > >> > > > > > > server and I'm getting the following error.
> > >> > > > > > >
> > >> > > > > > > Event ID: 20097
> > >> > > > > > > A user was unable to connect on port VPN4-4. No more
> > > connections
> > >> > can
> > >> > > > be
> > >> > > > made
> > >> > > > > > > to this remote computer because the computer has exceeded its
> > >> > client
> > >> > > > license
> > >> > > > > > > limit.
> > >> > > > > > >
> > >> > > > > > > I know for sure that the license limit isn't even close to
> > > being
> > >> > > > exceeded
> > >> > > > > > > and I have experience in setting up the DOD connections on NT
> > > and
> > >> > W2K
> > >> > > > so I
> > >> > > > > > > know how to set these connections up properly.
> > >> > > > > > >
> > >> > > > > > > The server is still happy to accept client VPN connections,
> > > the
> > >> > > > problem is
> > >> > > > > > > only with DOD routing connections.
> > >> > > > > > >
> > >> > > > > > > Has SBS 2003 RRAS been crippled ??
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> >
> > >> >
> > >> >
> > >
> > >
> >
> >
> >
- Next message: Donnie: "LAN Problem"
- Previous message: WK: "RE:Trouble adding clients. "list of users/computers could not be foun"
- In reply to: Andy: "Re: RRAS Dial on demand"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
