>I'm sure the ftp/ssh would also return if I didn't set the timeouts to such low numbers for those >services... >I know this probably isn't the right list to ask, but how can I tell if it's a networking issue? bad >cable? bad NIC?
Sorry if it's a stupid idea but couldn't you just ftp/ssh locally (address 127.0.0.1) on your defective-machine? At least this should tell you if the problem is hardware (NIC, cable) or software. Cyrille -------------------------------------------------------------------------------------------------------------- This mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, copying or transmission of this mail and/or any file transmitted with it, is strictly prohibited and may be unlawful. If you have received this mail by mistake, please immediately notify the sender as well as our mail administrator at [EMAIL PROTECTED], and permanently destroy the original as well as any copy therof.(Embedded image moved to file: pic19629.pcx)
pic19629.pcx
Description: Binary data
