ejunkie247
asked on
Need help resolving a WPA2-Enterprise authentication issue
I have a dedicated pfSense box. The lan port feeds into a basic 8 port switch which supports a LinkSys WRT 1900AC access point, an old DC (DC1), and an eSXI 5.5 box.
ESXI is running a new DC (DC2) that used to be physical, but was virtualized.
pfSense
---switch
------Access point
------DC1
------ESXI
oooooDC2 <--VM
I hope that generic graphic makes sense. Anyhow, my AP can authenticate against DC1 without any problems however I cannot get it to authenticate against DC2. All the services and firewall settings are setup correctly. This machine worked fine when it was physical. Also I have tested other services (my kids minecraft server was running on it for a while) and they are accessible from the WAN side of the pfSense box so I know I have connectivity.
I was thinking maybe I needed to connect the AP to the second ESXI ethernet port maybe?? I am an ESXI novice so any direction would be greatly appreciated. And if it helps, both the pfSense and ESXI boxes are running on Dell PowerEdge R210 servers. ESXI has 16GB of RAM and the pfSense has 8GB.
ESXI is running a new DC (DC2) that used to be physical, but was virtualized.
pfSense
---switch
------Access point
------DC1
------ESXI
oooooDC2 <--VM
I hope that generic graphic makes sense. Anyhow, my AP can authenticate against DC1 without any problems however I cannot get it to authenticate against DC2. All the services and firewall settings are setup correctly. This machine worked fine when it was physical. Also I have tested other services (my kids minecraft server was running on it for a while) and they are accessible from the WAN side of the pfSense box so I know I have connectivity.
I was thinking maybe I needed to connect the AP to the second ESXI ethernet port maybe?? I am an ESXI novice so any direction would be greatly appreciated. And if it helps, both the pfSense and ESXI boxes are running on Dell PowerEdge R210 servers. ESXI has 16GB of RAM and the pfSense has 8GB.
Craig Beck
Are you running NPS on DC2?
Did the IP address of DC2 change? Is it on the same subnet as DC1 and the access point? Can you browse the file shares on DC2 from another computer? I an wondering if you did the ESXi networking correctly. It should be in bridge mode.
ASKER
DC2 retained the same IP address. It is statically set by the pfSense box which supplies DHCP for the entire network so, yes, they are all on the same subnet. From a laptop I can access all devices on the network. If I move an object from one OU on either DC it replicates over to the other a few moments later. I can even use LDAP to authenticate logins to the pfSense box using DC2 to authenticate against. Near as I can tell, it is only the wireless that cannot authenticate against DC2.
Pardon me for letting me "newbness" show, but how do you check to see if it is in bridged mode in ESXI? For the most part I left everything default and only changed things that seemed like they may need to be changed such as adding the DNS and gateway.
Pardon me for letting me "newbness" show, but how do you check to see if it is in bridged mode in ESXI? For the most part I left everything default and only changed things that seemed like they may need to be changed such as adding the DNS and gateway.
ASKER
Craigbeck,
Yes, NPS is running on DC2. I replicated the setup on DC1 while DC2 was still a physical machine so I could switch between the two for maintenance and because DC1 is an aging system which I suspect will retire itself in the next year. At the time DC2 was virtualized it was being used as the day to day NPS server.
Yes, NPS is running on DC2. I replicated the setup on DC1 while DC2 was still a physical machine so I could switch between the two for maintenance and because DC1 is an aging system which I suspect will retire itself in the next year. At the time DC2 was virtualized it was being used as the day to day NPS server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
netstat -a does show that DC2 is listening for traffic in 389, 1812, and 1813 as I had expected. I ran wireshark and I did not get the traffic when I attempted to authenticate. On a whim, I decided to remove one hop. My AP has been physically connected to the switch and so was ESXI. So I directly connected ESXI to the AP and the traffic is getting through now. I still cannot authenticate, but at least I know the traffic is getting through. I am not sure what is going on with my switch that could be causing this, but at least it is a step forward.
Thank you!
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Craigbeck,
This is priceless. So prior to virtualization I had two drives in DC2, one for the OS and all data storage, the other was just transient data for the most part. Since the second drive was not linked to anything like network shares, I pulled it before virtualizing. It never occurred to me that my accounting log was being written to it. As such, my accounting log was pointed to a folder location that did not exist. I'm sure I must have overlooked some event logs pertaining to this.
Anyhow, I pointed the log to a freshly created folder that does exist and tried again. Low and behold it worked.
Between the switch issue and the log issue I was rapidly going mad. Thank you both for your assistance with this!!! :)
This is priceless. So prior to virtualization I had two drives in DC2, one for the OS and all data storage, the other was just transient data for the most part. Since the second drive was not linked to anything like network shares, I pulled it before virtualizing. It never occurred to me that my accounting log was being written to it. As such, my accounting log was pointed to a folder location that did not exist. I'm sure I must have overlooked some event logs pertaining to this.
Anyhow, I pointed the log to a freshly created folder that does exist and tried again. Low and behold it worked.
Between the switch issue and the log issue I was rapidly going mad. Thank you both for your assistance with this!!! :)
ASKER
The feedback and troubleshooting suggestions resolved the two contributing conditions that caused my problem ... Thank you both!!!