Incomming communication source on my Network port [on hold]











up vote
0
down vote

favorite












Is there a easy way to find out where from are comming some requests/packets to my application which is running on windows server and listening on 8081. We get invalid requests and full logs. Need to find out who is it.










share|improve this question















put on hold as off-topic by Vogel612, Brad Larson 23 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Vogel612, Brad Larson

If this question can be reworded to fit the rules in the help center, please edit the question.













  • As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
    – Vogel612
    yesterday










  • Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
    – Bishal Gautam
    yesterday















up vote
0
down vote

favorite












Is there a easy way to find out where from are comming some requests/packets to my application which is running on windows server and listening on 8081. We get invalid requests and full logs. Need to find out who is it.










share|improve this question















put on hold as off-topic by Vogel612, Brad Larson 23 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Vogel612, Brad Larson

If this question can be reworded to fit the rules in the help center, please edit the question.













  • As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
    – Vogel612
    yesterday










  • Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
    – Bishal Gautam
    yesterday













up vote
0
down vote

favorite









up vote
0
down vote

favorite











Is there a easy way to find out where from are comming some requests/packets to my application which is running on windows server and listening on 8081. We get invalid requests and full logs. Need to find out who is it.










share|improve this question















Is there a easy way to find out where from are comming some requests/packets to my application which is running on windows server and listening on 8081. We get invalid requests and full logs. Need to find out who is it.







networking






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









Vogel612

4,31353660




4,31353660










asked yesterday









Marek Ceizel

33




33




put on hold as off-topic by Vogel612, Brad Larson 23 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Vogel612, Brad Larson

If this question can be reworded to fit the rules in the help center, please edit the question.




put on hold as off-topic by Vogel612, Brad Larson 23 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Vogel612, Brad Larson

If this question can be reworded to fit the rules in the help center, please edit the question.












  • As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
    – Vogel612
    yesterday










  • Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
    – Bishal Gautam
    yesterday


















  • As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
    – Vogel612
    yesterday










  • Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
    – Bishal Gautam
    yesterday
















As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
– Vogel612
yesterday




As it is, you're asking for help in administrating a server in professional capacity. That's generally not on-topic on stack overflow. Please read the help center for more information on what kind of question is appropriate here. Thanks!
– Vogel612
yesterday












Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
– Bishal Gautam
yesterday




Please specify clearly how did you resolved that problem so that users may suggest if there exist an easier way than that of yours. Thanks!
– Bishal Gautam
yesterday












1 Answer
1






active

oldest

votes

















up vote
0
down vote













actually every communication can be checked by netstat.
netstat -ano | findstr 8081 should show all IP adresses which were contacting this port.



sorry to disturb ;)






share|improve this answer





















  • I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
    – Marek Ceizel
    yesterday




















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













actually every communication can be checked by netstat.
netstat -ano | findstr 8081 should show all IP adresses which were contacting this port.



sorry to disturb ;)






share|improve this answer





















  • I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
    – Marek Ceizel
    yesterday

















up vote
0
down vote













actually every communication can be checked by netstat.
netstat -ano | findstr 8081 should show all IP adresses which were contacting this port.



sorry to disturb ;)






share|improve this answer





















  • I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
    – Marek Ceizel
    yesterday















up vote
0
down vote










up vote
0
down vote









actually every communication can be checked by netstat.
netstat -ano | findstr 8081 should show all IP adresses which were contacting this port.



sorry to disturb ;)






share|improve this answer












actually every communication can be checked by netstat.
netstat -ano | findstr 8081 should show all IP adresses which were contacting this port.



sorry to disturb ;)







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Marek Ceizel

33




33












  • I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
    – Marek Ceizel
    yesterday




















  • I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
    – Marek Ceizel
    yesterday


















I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
– Marek Ceizel
yesterday






I have to add one comment. Our Problem is that something is trying to connect and it fails during the handshake phase. It looks like such requests would be not shown by netstat as the connection was never built. We will search for some network analyzer tool.
– Marek Ceizel
yesterday





Popular posts from this blog

'app-layout' is not a known element: how to share Component with different Modules

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

SQL update select statement