Why will a tcp server send a fin and ack immediately after accepting a connection

Question

0.00/5 (No votes)

See more:

Why will a TCP Server send a FIN and ACK immediately after accepting a connection:

Client->Server: SYN
Server->Client：SYN,ACK
Client->Server：ACK
Server->Client: FIN,ACK

run "tracert 127.0.0.1":

Through up to 30 jump points tracking
Route to [127.0.0.1] AM-201501021331:
1 <1 MS <1 MS <1 MS AM-201501021331 [no resources]
Track completion.

why result is "no resources";

What I have tried:

run "tracert 127.0.0.1", result is "no resources"

Posted 8-Mar-16 13:33pm

kxjhcs

Updated 9-Mar-16 16:34pm

Add a Solution

Comments

Richard MacCutchan 9-Mar-16 4:18am

127.0.0.1 is the loopback address. You need a real server application running.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Answer 1 · 2016-03-08T23:35:00

Solution 1

"[no resources]" is displayed instead of the IP address "[127.0.0.1]". While the tracing itself was succesful it indicates some kind of problem.

You may execute

nslookup 127.0.0.1

for further investigation and repeat that with the names localhost and AM-201501021331 (your computer's name).

Possible reasons are no DNS server configured / available or even no network connection.

At least you can execute tracert with an option to disable reverse name lookup:

tracert -d 127.0.0.1

Posted 8-Mar-16 23:35pm

Jochen Arndt

Comments

kxjhcs 9-Mar-16 22:35pm

nslookup 127.0.0.1
Server: UnKnown
Address: 10.1.33.7

name: localhost
Address: 127.0.0.1

run "tracert -d 127.0.0.1", result is "no resources" too;

Jochen Arndt 10-Mar-16 3:07am

"Server: UnKnown" = No DNS server.
I don't know your setup. But this should be fixed when your system is connected to a network.

kxjhcs · Answer 2 · 2016-03-09T16:34:00

Solution 2

nslookup 127.0.0.1
Server: UnKnown
Address: 10.1.33.7

name: localhost
Address: 127.0.0.1

run "tracert -d 127.0.0.1", result is "no resources" too;

Posted 9-Mar-16 16:34pm

kxjhcs