While searching for the book on Amazon, I came across this title:
C# for Java Programmers, which is published by a different publisher. It seems that the book was published before Microsoft's... So for people that might want an alternative perhaps this book will give a more unbiased view since it's not from the Microsoft Press...
I'm currently developing this client/server application and I have the server listening on port 31337. Anyways, I was testing my program from my home computer which is connected to the @home network. But for some reason it wouldn't connect to the server, keep on saying no route to host or some other error. I got my friend to try it, who is on @Home as well, and the same thing was happening. I know that the program works and couldn't figure out why it wouldn't connect. Anyways, after hours and hours of debugging, I tried running the server on another port and it worked just fine. I tested the client on another friend's machine that's just using a regular dialup account and it worked no problem. So it seems like for some reason @Home doesn't like port 31337.
Just curious if anyone else has run into this problem and if @Home is aware of it. Also, are there other ports that @Home doesn't allow?
Slashdot Mirror
While searching for the book on Amazon, I came across this title:
7 35 617791/qid=1031083751/sr=8-1/ref=sr_8_1/103-896164 2-1803861?v=glance&s=books&n=507846
C# for Java Programmers, which is published by a different publisher. It seems that the book was published before Microsoft's... So for people that might want an alternative perhaps this book will give a more unbiased view since it's not from the Microsoft Press...
http://www.amazon.com/exec/obidos/tg/detail/-/0
I wasn't aware that B.O. is using this port. Thanks for pointing it out.
I'm currently developing this client/server application and I have the server listening on port 31337. Anyways, I was testing my program from my home computer which is connected to the @home network. But for some reason it wouldn't connect to the server, keep on saying no route to host or some other error. I got my friend to try it, who is on @Home as well, and the same thing was happening. I know that the program works and couldn't figure out why it wouldn't connect. Anyways, after hours and hours of debugging, I tried running the server on another port and it worked just fine. I tested the client on another friend's machine that's just using a regular dialup account and it worked no problem. So it seems like for some reason @Home doesn't like port 31337. Just curious if anyone else has run into this problem and if @Home is aware of it. Also, are there other ports that @Home doesn't allow?