Non-Windows Clients Working Behind MS Proxy?
"Has anyone reverse-engineered the MS Proxy client and made a version that works with Linux? Would it be possible to run the windows proxy client under WINE (very doubtful i know). I would ideally like seamless access, the kind i get with my ipchains-based Linux box at home, but something that let me surf the Web, ftp, and telnet and SSH around would be ok.
I am real pissed off with the way that MS Proxy Server 2 has been deliberately engineered to work only with Windows clients, I didn't notice this mentioned in the anti-trust case, but it sure as hell should be.
Any help would be appreciated."
If Microsoft expects their server OS to be used as servers in heterogeneous environments, they really should start look at supporting clients that aren't Microsoft. Would it really be all that difficult?
You can have Junkbuster substitute the User Agent header with something that the proxy finds more to it's liking.
...phil
...phil
"For a list of the ways which technology has failed to improve our quality of life, press 3."
I did my own search and what I found is that it is probably an authentication issue, having to do with MS-Proxy expecting NT hashes instead of LAN hashes, which your Linux client is probably sending. I read in more than one place (unfortunately I can't give you a link) that it *can* be fixed, but nobody seems to know how!
I'm not an NT network administrator, I'm probably missing something, I may be downright wrong, but if I am I would like to hear from more enlightened people.
According to Freshmeat, there is a program called "Dante" which might help. I haven't tried it myself, though.
But my grandest creation, as history will tell,
But my grandest creation, as history will tell,
Was Firefrorefiddle, the Fiend of the Fell.
I used netscape at school when we where studying Unixware. All I did was point it to the proxy box and set the socks port. Never had any trouble.
The proxy client is only for programs that don't support http-proxy or socks.
Why not try putting a Windows NAT server on a workstation that is running the proxy client and point the non-Windows boxes at it as the gateway? I realize this is extra LAN traffic, but it could work.
Sure, but when youre stuck with a sys admin who 'just doesn't feel comfortable' working with anything that doesn't have a big, thorny Microsoft butt-plug attached to it, 'bad network grammar' seems to be a minor problem.
If it was up to me, i would simply remove MS Proxy Server 2 and replace it with a Linux (maybe BSD) box running ipchains (or the BSD equivalent) and squid. I would do it on a smaller box, for less money, and it would perform better, be more transparent to the users, support more OSes, and need very little maintenance.
I've told my sys admin all of this, and he thinks it would be a good idea, but basically, he's afraid of what happens when you try and remove that barbed butt-plug.
Its been jammed tightly up his ass for years, and it's working its way slowly towards the brain.
I gots ta ding a ding dang my dang a long ling long
Doesn't using the thing as a normal web proxy on port 80 (that's not a typo -- port eighty, same as normal http) work? Does for proxy 1, so long as the administrator has installed the normal web proxy module. (Yes, it does work. I surf from linux at home to a proxy 1 installation at work via a NT RAS PPP server). Course this is only FTP and HTTP, but better than nothing. Odd that it's port 80.. but that's microsoft for ya
The first link in the above paragraph should be this
Jim
Similar problems where discussed here less than a month ago.
:wq
...then it probably wants NT Challenge/Response security, and won't accept plain text. I've got a similar situation here - an MS Poxy Server that expects authentication, but various bits of client software that don't provide the authentication, or give it in the wrong format.
What i've done here is to set up an NT Server running Poxy, that routes upstream through the existing Poxy. It authenticates with that Poxy, but doesn't require authentication itself.
The result is, client app connects to 127.0.0.1:80 as a poxy, then my MS Poxy connects to the company's MS Poxy, using the authentication it's configured with. That connects out to the internet.
Of course, if you've got any influence over the main MS Poxy server, you can just turn off the authentication.
PigPog.
The evaluation of an action as 'practical' . . . depends on what it is that one wishes to practice.