<< I dought very much if Microsoft dosn't have this feature as well and your consultants really should know all this stuff including any work arounds its really why your paying them. Not for there ability to go around installing software on Macs and PC's without any serious configuration anyone can do that.>>
I spent an hour talking to one of their consultants yesterday who at no time mentioned the words "proxy client" as in "there exists one for windows but not for macs". They claim that they at present know of no workaround, and it sounds to me as though they have configured the system so that all messages must go through the proxy server. Problem is that telefinder for mac apparently cannot talk to the proxy server--it must completely avoid it and they either can't or don't want to do that.
I dont know what we pay them for--apparently to cause problems and then to "solve" them.
IF I want my application to go out some IP adress 1.2.3.4, it must first go to our proxy server whoae address is 10.11.12.13 There is no box in telefinder to tell the packets to go to 10.11.12.13 first and then go to 1.2.3.4--there is such a boz in netscape navigator, for example.
What I don't understand is what is so hard about this? For example, why doesn't the Mac have a place to say: send all the packets from networking programs to 10.11.12.13 if you click this box that says you are connected to a proxy server by that name? Presumably you would have to put some extra stuff into each packet but then everything would be cool. Conversely why couldn't the proxy server have some feature that, for all addresses other than those reserved for use by the intranet, it accepts the packets and transmits them to the outside world? What is the big deal about this? This sounds stupid--like stamp collecting (as someone more famous than me once said)--it's just keeping track of numbers--sheesh.
I should add that they are not blocking any ports--it's just that you can't get to them except through the proxy server.
