You know what, this is exactly why I love all you guys.. (and gals!) You've all given me loads of avenues to explore there that I hadn't thought of (because I just automatically assumed that I was at fault) in particular I like the McAfee policy update suggestion, because on Monday I had problems doing command-line FTP client connections to absolutely The Whole World, which 'they' (The Network Powers That Be Who Are A Law Unto Themselves) told me was due to a McAfee policy roll-out blocking port 21.. However that got fixed and I can 'native' FTP now. I'm surprised to see that 192.168.2.1 address in there - that is NOT my workstation, that is some 172.17.xxx.xxx address. So where has that 192 one come from? Is McAfee routing it through some sort of proxy, I wonder? Time for a chat with The Network Boys in the morning (it's 11:30pm here in the 51st State at the moment), I suspect though, I think I *know* how the conversation is going to go.. something along the lines of "..Changed? No, nothing's changed.. ..Nah, nothing we would do would affect you in *that* way.." etc Thanks again folks for all the pointers and suggestions of which way to go. At least I know I'm not going mad. Unless we all are.. Brian - This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction NetworkServices. Any unauthorized review, use, disclosure or distribution isprohibited. If you are not the intended recipient, please contact thesender by reply e-mail and destroy all copies of the original message.
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
