Firewall Mysteriously Turning On After Enabling DHCP - XP SP3

When trying to change corporate PCs from static assignments to DHCP, I
am getting all sorts of results (I inherited this situation). The
oddest and most frequent one I am running into is that the firewall is
turning on -- not good.

The PCs do not have admin rights, and many a GPO is applied (I can not
find anything in the policies that would cause this)


Since PCs do not have admin rights, here are the two methods I have
tried to change IP from static to DHCP (inc. DNS server assignments):


Method 1 -- PSEXEC
psexec \\PCNAME -s netsh interface ip set address name="Local Area
Connection" source=dhcp
psexec \\PCNAME -s netsh interface ip set dns name="Local Area
Connection" source=dhcp
--note: a "psexec \\rad03 -s netsh firewall set opmode disable"
issued prior to does not help


Method 2 -- For Giggles, Remote Control & RUNAS
Dameware to PC, then:
runas /env /user:administrator@domain "netsh interface ip set address
name=\"Local Area Connection\" source=dhcp"
runas /env /user:administrator@domain "netsh interface ip set dns name=
\"Local Area Connection\" source=dhcp"


I've tried various VB scripts also -- to no avail.


Summary, the DHCP command typically "takes" and the PC will get an
assignment from DHCP -- BUT the firewall will turn on.


This is driving me insane. Chicken dinner to the winner.


Thanks.