Is that what you use for home? :)
On Wed, Feb 8, 2017 at 1:06 PM, Kennedy, Jim
<[email protected]> wrote:
> Yea, yours sounds a tad different than mine. Shame, my guest wireless dhcp
> server is named PropOfFBI That alone was worth the effort.
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Kurt Buff
> Sent: Wednesday, February 8, 2017 4:01 PM
> To: ntsysadm
> Subject: Re: [NTSysADM] Odd problem with DHCP
>
> I think I'll start with a capture, and see what PA has to say about it.
>
> I really don't want to stand up a separate machine just for DHCP in the guest
> wireless network, and if the PA isn't seeing the DHCP request so as to issue
> an address, it doesn't fill me with hope that it would be any better being a
> DHCP relay.
>
> Kurt
>
> On Wed, Feb 8, 2017 at 12:36 PM, Kennedy, Jim <[email protected]>
> wrote:
>> Used to see it a lot until we started using my Windows Servers for dhcp
>> instead of Cisco. It was a nightmare, took it to TAC and MS support with
>> zero luck.
>>
>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of Kurt Buff
>> Sent: Wednesday, February 8, 2017 3:28 PM
>> To: ntsysadm
>> Subject: [NTSysADM] Odd problem with DHCP
>>
>> All,
>>
>> We've seen three instances lately where Windows workstations are failing to
>> get an address via a wireless connection.
>>
>> The DHCP server in this case is our firewall (a Palo Alto 3000 series),
>> serving the guest network only.
>>
>> The three machines are a desktop destined for a trade show, a roaming laptop
>> used in our lab, and a visiting vendor rep.
>>
>> The vendor rep was running Win8.1, the others are win10.
>>
>> The only commonality I saw was that each of the machines was running some
>> sort of virtualization - two are using hyper-v, and one using virtualbox.
>>
>> I didn't have time to set up a packet capture on the firewall, but I was
>> able to tail the dhcp log on the firewall, and in each case I never saw the
>> request hit the log.
>>
>> In all cases, shutting down the services related to the virtualization did
>> not solve the problem.
>>
>> Has anyone seen anything like this before, or have any ideas on how to
>> troubleshoot it?
>>
>> I'm about to remove the virtualization config from our two machines to see
>> if that makes a difference, but if that's the problem, then I'd love to know
>> how to fix it, because the virtualization they're running is part of their
>> required configuration.
>>
>> Kurt
>>
>>
>
>
