Discussion Locked

win2k3 AD and win2k IAS

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Scenario:
NT4 domain, win2k stand-alone with IAS authenticating users agains SAM, stand-alone win2k3 DNS server with primary forward and reverse lookup zones (dynamic update disabled).
Last week I've attmpted to upgrade to AD. It went as follows:
Set up a new NT PDC.
Synchronized the entire domain, took old PDC off line.
Started the upgrade on the new PDC to win2k3.
Finished off the upgrade, which went with no issues.
Verified user account replication, authentication.
Registered the stand-alone 2k IAS server with AD (I verified the computer account exists in AD in the members of RAS and IAS access group).
Two problems I encounered:
1. When users try to connect via VPN or Dial-Up, it keeps promting them for the password. On the IAS server I keep getting:

Access request for user cfallis was discarded.
Fully-Qualified-User-Name = DOAMIN\user
NAS-IP-Address = x.x.x.x
NAS-Identifier =
Called-Station-Identifier = 8378
Calling-Station-Identifier = xxxxxxxxxx
Client-Friendly-Name = Dial-Up Chassis
Client-IP-Address = x.x.x.x
NAS-Port-Type = Async
NAS-Port = 2835
Reason-Code = 6
Reason = The server is unavailable.

I can see each server from either one, ping them...and what not.
The authentication works again after I reverted back to NT4 Domain

2. On the stand-alone 2k3 DNS server I have a lot of entries in both forward and reverse lookup zones. It's configured to load them from file. How can I incorporate them to the newely set up AD integrated DNS on the DC.
I changed the primary zones to secondary on the stand alone DNS and allowed repliacation between the two. That resulted in wiping all entries out of the stand alon dns.
I was going to change the AD integrated zone to load from file and just copy and pasted the entries, but that's not allowed with AD integrated zones.

4 replies

by cg it

let me get this straight your DC was NT4 and you wished to upgrade that NT4 DC to WK3 and incorporate AD to your network. What you did was make a seperate NT4 DC and allowed replication between both NT4 DC's, then took one off line and upgraded it to WK3 then put it back online, and took the other NT4 DC offline and then instituted AD on the network via the WK3 DC. After that you made the W2K ISA server as a member server of the WK3 AD network for ISA services.

Users who try to access the network via VPN or dialup through ISA server are prompted for a user name and passwork but connection and authentication fail.

What is your ISA server H323 Gatekeeper, and ISA Server Access Policy IP packet Filter setup for VPN and also how is RRAS setup for authenticating Domain account remote users?

Also did you dcpromo demote the NT4DC to a member server then remove that as a member server from the domain?

by quake

No, no
The Win2k IAS was already in place before the AD upgrade. It's up and working in the NT domain as a stand alone server just fine.
I set up a new BDC and promoted it to PDC. As a result the old PDC became a BDC and I took it off line just in case the upgrade fails (which it did). To roll back all I had to do is
Unplug the newely created win2k3 AD DC, plug in the BDC (PDC before upgrade) and promote it back to PDC.
The win2k IAS server stopped working after the upgrade, but once I rolled back it's working again.

by quake

I just read on technet that it takes a while for AD to register the IAS due to its cashing or something like that. They recommend you restart the IAS server if you want the changes to take place immediately. I have not done that, maybe that's the problem?

This discussion is closed to new replies.