I'll check tomorrow and follow up after I talk with the admin that disabled SOCKS.

Had to check so I could get some sleep:

At the moment, we are using ISA to block SOCKS. Sorry that I said that it was a script. Bad information, you caught me, busted .....

But, what we had in place was a script that pointed people to the firewall before we implemented ISA. The part that blocked SOCKS went something like this:

# SOCKS: establishing a connection
ipchains -A output -i $EXTERNAL_INTERFACE -p tcp -y \
-s $IPADDR \
-d $ANYWHERE $SOCKS_PORT -j REJECT

# SOCKS incoming connection
ipchains -A input -i $EXTERNAL_INTERFACE -p tcp -y \
-d $IPADDR $SOCKS_PORT -j DENY

I hope this gives you an Idea, If not, let me know and I'll put more of the rule here.......
Once again, Sorry that I said it was a Logon Script.
However, there is an app out there call socksdis.exe that will disable socks or you can do it manually be renaming the SOCKS.CNF file, but I don't know what this will cause..........
Man, Now I feel like I'm really not helping much at all..........