Rank: Newbie
Groups: Member
Joined: 7/10/2008
Posts: 1
|
I posted yesterday regarding this problem, and then you folks went off-line and also the thread seems to have disappeared.
Here is the FIX:
Our app runs long exercises against a private network DB and the app runs locally on our laptops. So, we use a script to start the local web server and the app. I had not specified a port in the scrip and so it defaulted to port 80. Port 80 and it's apparent protections on our laptops stops the communication between code behind and the web page. Adding a port (4950 or something) to the script solved the problem.
Conclusion: on locally run apps, we need a different port than 80 for communication to take place.
Thanks for your help. It got me testing and thinking.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi Lee,
Our database was damaged yesterday and a few posts, including yours were lost. I sincerely apologize for the problem.
We are very glad that you figure out the problem. This would definitely not be something that we can think of. :)
Please feel free to let us know if you have any other questions.
Thanks
|