Re: RRAS (2k3 server): dial-up clients can't authentificate
From: Dana Brash (dbrash_at_gmail.com)
Date: 11/09/04
- Next message: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Previous message: Dana Brash: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- In reply to: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Next in thread: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Reply: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Reply: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Nov 2004 14:55:56 +0800
<snip>
DHCP server is on the same computer. (WINS, DNS too). RRAS use static adress
pool 192.168.100.1-192.168.100.24
In local network are two routed subnets 192.168.0.0, 192.168.2.0. They are
routed by RRAS
</snip>
Why are you using a different subnet for dial-in users? Are you also
routing your dial-in subnet to the internal subnets as well?
-- HTH, =d= Dana Brash MCSE, MCDBA, MCSA dbrash@NOSPAM.gmail.com "Iv Michael" <IvMichael@discussions.microsoft.com> wrote in message news:3571FF00-4520-4C3F-A1D0-6C4715D28542@microsoft.com... > Comments below... > >> OK, so you have some sporadic behavior, and sometimes users can connect. > Yes. > >> Are you talking about the same user is able to connect on one try, and >> then >> later they are not able to connect? > Yes. > This situation happened with two users (testers), they connected to two > analog modems (each user trying to connect to both modems). > >> >> Since SP1 is not due out until early 2005, (and I don't have 2 ISDN lines >> to >> play with at home) I can't repro your environment here. If you are >> running >> a beta version of SP1, then you might try removing it. However, I don't >> believe this is a 'patch' issue.... > OK, thanks. I'll try to remove SP1. > >> Multiple modems is probably not an issue, but I always like to start >> simple >> when troubleshooting a problem. If you can eliminate all but one of the > //over steps skipped but not forgotten. > OK, no problem, I can do it now. > >> Also explain where your DHCP server is and how you've got RRAS handing >> out >> leases. > DHCP server is on the same computer. (WINS, DNS too). RRAS use static > adress > pool 192.168.100.1-192.168.100.24 > In local network are two routed subnets 192.168.0.0, 192.168.2.0. They are > routed by RRAS > Destination Network mask Gateway Interface Metric View > 192.168.0.0 255.255.255.0 192.168.0.2 Local Area Connection 1 Both > 192.168.2.0 255.255.255.0 192.168.2.2 Local Area Connection 2 1 Both > 192.168.100.0 255.255.255.0 192.168.100.1 Local Area Connection 1 Both > > Now i'm in process of migration from NT4 to 2k3 domain, so i have two DC > in > network (domains have trusts, old server now is PDC, master browser, and > file > server only). Users moved by ADMT2 and can logged in in both domains. > Dial-in users logged in to new domain only.
- Next message: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Previous message: Dana Brash: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- In reply to: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Next in thread: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Reply: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Reply: Iv Michael: "Re: RRAS (2k3 server): dial-up clients can't authentificate"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|