I have already ask this question in another thread but wrong topic. I hope now that anyone here already heard from that issue. The problem is that I receive the above mentioned error when I try to open an attachment of a service call or if I try to save one where I put an attachement on.
Actually we experience this problem not on all clients only some of them have this error. The settings are all ok I guess, because it worked for couple years now. We had some update of the whole image (windows)those guys are looking at it also. May be some one has another idea. Thanks
I've also faced that error before. There is a known error corrected with service pack 15.Some clients that have two network interface cards in the same system are getting the following error message when they try to attach a file in Service Desk:
FTP-Error: 500 Invalid PORT Command
Workaround: Disable one of the network interface cards on client.
The above post is correct about the two network cards. Most often this happens with devices that have a wireless card and the users then return and dock their workstations without disconnecting the wireless card. In general, having 2 network cards attached simultaneously is a snafu to be avoided, so it would be a good idea to ask users to disconnect their wireless whenever docking or else have them use wireless all the time. Unless you want them routing packets with their workstations that is. :P
We're on SP10, and I only see that error when someone has both cards on simultaneously. I wouldn't upgrade to SP15 just to fix that issue, since no one should have two network cards running at once. (Causes other networking issues.)
If the devices were rebooted, are you sure it didn't re-establish connection with the wireless network when they came back up? Sorry, just not clear if you disabled the wireless or physically removed the card and wanted to verify.
Also, is it possible to try physically disconnecting one of the affected devices' network cables and use just the wireless for a moment? It would be a good idea to verify that we're on the right track, so this would be a good troubleshooting step to make sure we can get it to work when there's definitely only one network connection.
yes we made sure the connections were disabled, they even removed the card at last and even then same error message. We have this on a windows 2000 clients and on older computers it works and on the newest image from windows what they updated it does not. Some idea what might cause the trouble.
I've had the same problem with 2 NIC's. Fixed simply by swapping the two cables over. Never understood it fully but someone sugegsted it was something to do with the primary NIC being on the wrong LAN connection. Whatever that means....it seemed to work in my case.
Alright, so can you ftp to the server manually from one of the affected client machines? If you can't ftp, it's still a networking issue or maybe an OS problem. If you can ftp, then you've got an SD client issue.
If you don't have an FTP client, go to a command-line and type "ftp [your server]". Then try changing directories and maybe retrieving a file. See if anything looks out of the ordinary.
Or you could just try SP15 if you want to overkill it.
Hello: You mentioned that the "older Win 2000" systems didn't seem to have this problem. Are the problem systems running Windows XP? And more importantly SP2.
SP2 automatically turns on the firewall function and that could be causing your error. I ran into that issue myself. Further maybe the users turned on the firewall themselves even if using SP1 or none at all.
What was the fix on the Cisco VPN Concentrator!? You state it was a problem with the Cisco VPN, but not what the fix was. We are experiencing the same issue, but have not been able to determine the fix. Please advise.
What they just did was to uninstall the Cisco VPN Client and reinstalled it. We also made sure that if the client were connected to the network, that the wireless network card was disabled. Then everything was fine and worked. What actually went wrong with the VPN Client nobody knows...hhhmmm I hope that will help. Meanwhile we have SP 15 and nobody is experiencing the error.