This issue is one that has taken me and our IT department at our company many hours to pinpoint.
The problem only appears on Windows server 2008, windows 7 and windows 8. On Windows XP or Windows server 2003 we have no issues.
We are having a program that we have developed internally in our company. The program works fine and the issue is not specific to this program.
The program uses localhost to communicate with other programs running on the computer using webservices. The issue at hand is that this communication doesn't work if the program is located in the users Home folder.
Having used many hours finding out why this is we recently realized that problem disappears if the user has access to all parent folder in the UNC path to the executable file.
So if the home drive is mounted at H: = \SomeServer\hdrive$\SomeUser and the user has no acces to \SomeServer\hdrive$ then our program gets TCP errors and the webservices wont work.
If the user then gets just the "List folder contents" permission on that path, then the webservices work.
The program otherwise runs fine. We have checked that all dll files are linked successfully and that no other errors occurs.
This appears to be something that the OS is doing. Does anyone know why this happens?