|
Home > Archive > Radius Server > May 2004 > 802.1x and DHCP Failure
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
802.1x and DHCP Failure
|
|
|
| Did you solved this problem, the same things is happening
to me. I'm Using a netgear ME103 AP win w2k3m, IAS.
Thanks,
>-----Original Message-----
>Hi,
>I am trying to setup radius authentication. Having
failed on our production
>network I have set up a test setup consisting of a 2003
standard sever and a
>laptop running XP sp1.
>I have applied all service packs/updates I can find.
>I have tried both Dlink 900AP and 2000AP's and Dlink
650+ & G650 PCMCIA
>cards, all with the latest drivers.
>The laptop logs on and obtains an ip address correctly
using a wired
>connection.
>
>When connecting by wireless I always get an Automatic
Private IP Addressing
>(APIPA)
>
>In the technet article "Troubleshooting Windows XP IEEE
802.11 Wireless
>Access" it states:
>"If the wireless adapter has an Automatic Private IP
Addressing (APIPA)
>address (169.254.0.0/16) or the configured alternate IP
address, then
>authentication has failed and the Windows XP wireless
client is still
>associated with the wireless AP" but the IAS log and AP
log indicate that
>authentication was successful.
>I have tried everything but to no avail!
>Any help greatly appreciated!
>
>RogerC
>Test setup:-
>The test domain is 'ROGERDOM', server 'win2k3s' and
laptop 'ROGERLAP' and
>user logon of rogerc.
>Server Event Log entries:
>
>Event Type: Information
>Event Source: IAS
>Event Category: None
>Event ID: 1
>Date: 11/04/2004
>Time: 01:04:34
>User: N/A
>Computer: WIN2K3S
>Description:
>User host/ROGERLAP.rogerdom.com was granted access.
> Fully-Qualified-User-Name =
rogerdom.com/Computers/ROGERLAP
> NAS-IP-Address = 192.168.8.50
> NAS-Identifier = MY-DWL-900AP+
> Client-Friendly-Name = 900AP
> Client-IP-Address = 192.168.8.50
> Calling-Station-Identifier = 00-80-C8-07-11-47
> NAS-Port-Type = Wireless - IEEE 802.11
> NAS-Port = 0
> Proxy-Policy-Name = Use Windows authentication for all
users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Policy-Name = WIRELESS access policy
> Authentication-Type = PEAP
> EAP-Type = Secured password (EAP-MSCHAP v2)
>
>Event Type: Information
>Event Source: IAS
>Event Category: None
>Event ID: 1
>Date: 11/04/2004
>Time: 01:08:02
>User: N/A
>Computer: WIN2K3S
>Description:
>User ROGERDOM\rogerc was granted access.
> Fully-Qualified-User-Name = rogerdom.com/My Users/Roger
xxxxxx
> NAS-IP-Address = 192.168.8.50
> NAS-Identifier = MY-DWL-900AP+
> Client-Friendly-Name = 900AP
> Client-IP-Address = 192.168.8.50
> Calling-Station-Identifier = 00-80-C8-07-11-47
> NAS-Port-Type = Wireless - IEEE 802.11
> NAS-Port = 0
> Proxy-Policy-Name = Use Windows authentication for all
users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Policy-Name = WIRELESS access policy
> Authentication-Type = PEAP
> EAP-Type = Secured password (EAP-MSCHAP v2)
>
>AP log:
>
>Apr/13/2004 00:03:04 Send Accounting login message
ROGERDOM\rogerc
>Apr/13/2004 00:03:03 Authentication success 00-80-C8-07-
11-47
>Apr/13/2004 00:03:03 EAP-Success 00-80-C8-07-11-47
>Apr/13/2004 00:02:53 EAP-Response/Identity
ROGERDOM\rogerc
>Apr/13/2004 00:02:53 EAP-Request/Identity
>Apr/13/2004 00:02:53 Wireless PC connected 00-80-C8-07-
11-47
>Apr/13/2004 00:02:45 EAP-Response/Identity
ROGERDOM\rogerc
>
>
>
>
>
>.
>
| |
| RogerC 2004-04-23, 6:35 pm |
| Hi anonymous,
I am now working and obtaining an ip address's correctly - but don't ask me
how!
I went through the setup of IAS, Client, AP so many times I don't know what
was the factor that got me going.
I cannot break it and get back to the position where both computer and user
authenticate ok but don't get an IP. I will go through my setup and post
the settings I am using when I get time.
Are you using Dlink AP's? It might help knowing this to see if it common
with them.
Regards,
RogerC
<anonymous@discussions.microsoft.com> wrote in message
news:2abd01c42864$573b4800$a401280a@phx.gbl...[vbcol=seagreen]
> Did you solved this problem, the same things is happening
> to me. I'm Using a netgear ME103 AP win w2k3m, IAS.
> Thanks,
> failed on our production
> standard sever and a
> 650+ & G650 PCMCIA
> using a wired
> Private IP Addressing
> 802.11 Wireless
> Addressing (APIPA)
> address, then
> client is still
> log indicate that
> laptop 'ROGERLAP' and
> rogerdom.com/Computers/ROGERLAP
> users
> xxxxxx
> users
> ROGERDOM\rogerc
> 11-47
> ROGERDOM\rogerc
> 11-47
> ROGERDOM\rogerc
| |
|
| Were you able to figure out the solution, I'm using a
netgear ME103 AP.
THanks,
>-----Original Message-----
>Hi anonymous,
>I am now working and obtaining an ip address's
correctly - but don't ask me
>how!
>I went through the setup of IAS, Client, AP so many
times I don't know what
>was the factor that got me going.
>I cannot break it and get back to the position where
both computer and user
>authenticate ok but don't get an IP. I will go through
my setup and post
>the settings I am using when I get time.
>Are you using Dlink AP's? It might help knowing this to
see if it common
>with them.
>Regards,
>RogerC
>
><anonymous@discussions.microsoft.com> wrote in message
>news:2abd01c42864$573b4800$a401280a@phx.gbl...
happening[vbcol=seagreen]
2003[vbcol=seagreen]
IEEE[vbcol=seagreen]
IP[vbcol=seagreen]
AP[vbcol=seagreen]
all[vbcol=seagreen]
Users/Roger[vbcol=seagreen]
all[vbcol=seagreen]
07-[vbcol=seagreen]
07-[vbcol=seagreen]
>
>
>.
>
| |
| Harold 2004-05-24, 1:59 am |
| The DWL-900AP+ advises me of ...
May/24/2004 16:12:20 EAP-Response/Identity DRS\armada
May/24/2004 16:12:20 EAP-Request/Identity
May/24/2004 16:12:18 Wireless PC connected
May/24/2004 16:11:19 Send Accounting login message DRS\armada
May/24/2004 16:11:19 Authentication success
But the client doesn't obtain a DHCP address.
Pings return 'destination unreachable'... |
|
|
|
|