Im developing an UDP client-server application using sdl-net. Since I
wrote the first lines of code I have been testing in both Windows and
Linux, and the code works. But some day, for some unknown reason, the
code stopped working in Windows. When I run the client and server in my
linux box I can connect perfectly. When I run the client on windows, it
cant connect, not to the server in linux or in the same windows host.
Also, if I run the server in windows and the clint on linux, the
connection fails.
CAn somebody give me an idea about what could be happening here?–
Roger D. Vargas
Formatur Santiago
This could be a normal connectivity troubleshooting. I believe you
have some security software on that windows box. Well, some of the
most popular firewalls like WinXP’s Firewall, Norton internet security
and others will change their protective behavior sometimes and may
start blocking networking services for no reason. Just try disabling
all security software at once, see if that helps, if not problem is
somewhere else, if it does help then you know you have to reconfigure
your security software.
Good luck,
SimonOn 2/18/06, Roger D. Vargas wrote:
Im developing an UDP client-server application using sdl-net. Since I
wrote the first lines of code I have been testing in both Windows and
Linux, and the code works. But some day, for some unknown reason, the
code stopped working in Windows. When I run the client and server in my
linux box I can connect perfectly. When I run the client on windows, it
cant connect, not to the server in linux or in the same windows host.
Also, if I run the server in windows and the clint on linux, the
connection fails.
CAn somebody give me an idea about what could be happening here?–
Roger D. Vargas
Formatur Santiago
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
This could be a normal connectivity troubleshooting. I believe you
have some security software on that windows box. Well, some of the
most popular firewalls like WinXP’s Firewall, Norton internet security
and others will change their protective behavior sometimes and may
start blocking networking services for no reason. Just try disabling
all security software at once, see if that helps,
I’m sure you meant that in all seriousness, but it elicited a chuckle from
me. Thanks for brightening my day 
JeffOn Saturday 18 February 2006 15:55 pm, Simon wrote:
TCP is fairly easy to troubleshoot by simply using telnet to test.
Unfortunatley this does not work with UDP. For UDP I have found that a
utility like netcat to be invaluable for troubleshooting.
Also, if this was working but no longer works, have you changed the
code in the intrim? If yes, can you test if the old code still works?
If no, were there any changes in the system configurations?
Another strategy would be to reduce down to have some small simple UDP
test programs and make sure they work, and then build from there.
ChrisOn 2/18/06, Roger D. Vargas wrote:
Im developing an UDP client-server application using sdl-net. Since I
wrote the first lines of code I have been testing in both Windows and
Linux, and the code works. But some day, for some unknown reason, the
code stopped working in Windows. When I run the client and server in my
linux box I can connect perfectly. When I run the client on windows, it
cant connect, not to the server in linux or in the same windows host.
Also, if I run the server in windows and the clint on linux, the
connection fails.
CAn somebody give me an idea about what could be happening here?
–
E-Mail: Chris Nystrom
http://www.newio.org/
AIM: nystromchris
El s?b, 18-02-2006 a las 21:52 -0600, Chris Nystrom escribi?:
Im developing an UDP client-server application using sdl-net. Since I
wrote the first lines of code I have been testing in both Windows and
Linux, and the code works. But some day, for some unknown reason, the
code stopped working in Windows. When I run the client and server in my
linux box I can connect perfectly. When I run the client on windows, it
cant connect, not to the server in linux or in the same windows host.
Also, if I run the server in windows and the clint on linux, the
connection fails.
CAn somebody give me an idea about what could be happening here?TCP is fairly easy to troubleshoot by simply using telnet to test.
Unfortunatley this does not work with UDP. For UDP I have found that a
utility like netcat to be invaluable for troubleshooting.
Yes, I have noticed that.Also, if this was working but no longer works, have you changed the
code in the intrim? If yes, can you test if the old code still works?
If no, were there any changes in the system configurations?
Sorry, I dont have the old code. The only configuration change I
remember is that I upgraded linux from fedora 2 to CentOS 4.2, and yes,
that brought me a lot of connection problems with games like Anarchy
Online and Planeshift, that no longer works.
After another test, I found that I cant connect to the linux server from
another PC. Obviously this is a connectivity problem, but why the
windows client cant connect to a server in the same windows PC? Or why
the windows server cant be accessed from another PC?> On 2/18/06, Roger D. Vargas wrote:
–
Roger D. Vargas
Formatur Santiago
I’m sure you meant that in all seriousness, but it elicited a chuckle from
me. Thanks for brightening my day
You never did connectivity troubleshooting for windows before? I work
for an ISP and do this every day. We disable security software all
the time, Norton and McAfee always blocks everything for no reason.
Sometimes the WinXP firewall even does the same tricks.
Many times it’s just a matter of configuration of those security
software, but it seems some of them (norton, mcafee?) will change
their behavior to protect users better and that’s when stuff start
being blocked. Just shut it down for one minute, just to see if
security software is responsible.
Simon