116 reputation
6
bio website l46kok.blogspot.com
location Seoul, South Korea
age 26
visits member for 2 years, 1 month
seen Dec 8 at 14:04

Just an average joe coder for now.

Aspiring to be one of the greatest developers ever.

It never hurts to dream.

Interests in:


Mar
24
accepted Would blocking an entire ip range of a country potentially hinder performance?
Mar
18
asked Would blocking an entire ip range of a country potentially hinder performance?
Aug
22
comment How does IPv4 Subnetting Work?
I'm going to upvote this answer to make sure that two answers are kept in order.
Aug
22
awarded  Supporter
Mar
5
awarded  Autobiographer
Nov
14
comment Connecting to database without instance name
Sorry, I meant instance name. What I want to do is set a default instance but the only way I know to do this is to do a complete reinstallation of SQL Server 2008. I was hoping for a better solution.
Nov
14
asked Connecting to database without instance name
Nov
6
awarded  Tumbleweed
Oct
29
accepted Windows server 2008 rejecting packets from client
Oct
25
awarded  Teacher
Oct
25
answered Windows server 2008 rejecting packets from client
Oct
25
comment Windows server 2008 rejecting packets from client
And this one from the server's perspective imageshack.us/a/img571/5593/79502371.png Edit: Wrong link. Updated with new one.
Oct
25
revised Windows server 2008 rejecting packets from client
added 1 characters in body
Oct
25
comment Windows server 2008 rejecting packets from client
@DavidSchwartz OH ok. I'm pretty new to this stuff so I apologize about my ignorance. From looking at the wireshark packet, yes the TCP handshake seems to be completing as server is sending a reply back to the client. This is a snapshot of wireshark diagnostics from the client's perspective. imageshack.us/a/img837/1411/14289430.png. I don't know why I wrote external IP up there, I guess I was zoning out.
Oct
25
comment Windows server 2008 rejecting packets from client
Turns out that the server is receiving the packets so this is where it led me to believe that it's actually the O/S (Win server 2008) blocking the packets being sent to the server application.
Oct
25
comment Windows server 2008 rejecting packets from client
@DavidSchwartz Maybe I'm doing a bad job at explaining the problem here D:. First of all, server is not behind an NAT. The server application that I wrote opens a TCP socket and starts running on port 5055. When the client tries to connect to the server to port 5055, the server application never receives any packets from the client, so the server application can't send a response out to begin with. This is where I ran wireshark diagnostics to make sure that the server computer itself is receiving the packets.
Oct
25
awarded  Editor
Oct
25
comment Windows server 2008 rejecting packets from client
@DavidSchwartz As said in the question, the server (NIC) receives the packets but does not reply because the server application isn't receiving the packet.
Oct
25
revised Windows server 2008 rejecting packets from client
added 118 characters in body
Oct
25
comment Windows server 2008 rejecting packets from client
@DavidSchwartz I did exactly that and well, no luck D: