Non-Windows Clients Working Behind MS Proxy? 17
"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?
Use Junkbuster (Score:4)
...phil
Is MS-Proxy really refusing to route? (Score: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.
Re:Is MS-Proxy really refusing to route? (Score:1)
Dante (Score:1)
According to Freshmeat [freshmeat.net], there is a program called "Dante" which might help. I haven't tried it myself, though.
But my grandest creation, as history will tell,
Re:Is MS-Proxy really refusing to route? (Score:3)
Dave
Netscape for SCO work NP (Score:1)
The proxy client is only for programs that don't support http-proxy or socks.
Double Proxy? (Score:1)
Re:Double Proxy? (Score:1)
I presumed this just wouldn't work, but now i think about it, it *should* work fine.
A bit more network traffic is a small price to pay for feeling at home on my computer again.
Thanks
Re:Double Negative? (Score:1)
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.
Should work anyway (Score:1)
Re:Is MS-Proxy really refusing to route? (url fix) (Score:3)
Jim
Re:Dante (Score:2)
Re:Is MS-Proxy really refusing to route? (Score:3)
The MS Support KB articles Q245237 and Q218484 try to describe how to change configuration settings to allow Netscape to work with MS Proxy (I'd give links, but the MS KB web format has broken links in the past -- and even the MS Home Page [microsoft.com] doesn't have the correct link to the current MS Support home page).
Related topic discussed (Score:1)
If it's asking for security... (Score:1)
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.
Two possibilities (Score:1)
Re:Use Junkbuster (Score:1)