hosts, and we can’t change passwords even from WXP clients. I’m too lazy
to sniff out the packets going to and from ligaya, and
besides, I wouldn’t know where to look if it bites me in the nose. I’ve tried searching the AD through
ldapsearch.Anonymous
ldapsearch can query the directory, but when itcomes to authenticated queries, it’s a no go. Google has lots of links for me, and I’ve exhausted each one. I’m
itching to post in some mailing lists, but I’m still restraining myself
until I can get *at least* a fix on what’s really happening. Besides, it
could be a W2K3 issue, and from what I have read in the local MS forums,
I doubt if they are any help. So back to dipping my nose on the docs. Also: I wonder why using the automatic proxy configuration script
works for Mozilla and Firefox (a derivative of Mozilla), and not for IE.
Another MS quirk? I’ve managed to create a workaround, though: edit the
registry, hard-code the proxy configuration there. Here’s what I did. I created a text file,
proxy.regcontaining the following:
REGEDIT4
I saved it in a public share on the server, created a login script[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings]
“ProxyEnable”=dword:00000001
“ProxyServer”=”xxx.xxx.xxx.xxx:xxx”
“ProxyOverride”=”.foo;.bar;.baz;”
that invokes
regedit /s \\path\to\public\share\proxy.reg
and have it executed every time a user logs in. Should work. I hope.

0 Responses to “Network configuration, day four”
Leave a Reply