You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
Interesting concept, however from the wireshark analysis it seems like the packets are identical in sequence, up until the part where it stops working of course... also, the most important bit which I'll edit in my question - I don't need to run Procmon each time for the application to work - if I reboot the workstations everything still works! Seems like a one time modification...– lcamCommented Aug 22, 2017 at 11:45
-
I acknowledge the dead look is a remote possibility. But still it's feasible. The order or the packets is not critical for producing the dead lock, but the timing. If SW2 replies very quickly and SW1 is not well designed, it maybe missed up the packet and gets stacked waiting for it. It's like getting just on time to the bus stop, but nobody is waiting. You don't know if the bus is to come, or if it's gone. Check the timing of the packets from the different servers, or try running any software -other than Procmon- which creates a heavy load on the server to see if you get the same effect.– piedramaniaCommented Aug 22, 2017 at 12:20
-
Thanks for the explanation piedramania - I am now looking into replicating the problem on an offline workstation so I could experiment on the issue. I'll give it a go. Thanks!– lcamCommented Aug 22, 2017 at 12:23
-
This explanation does not hold if everything now works and keeps on working without Process Monitor.– harrymcCommented Aug 22, 2017 at 12:24
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_`
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. windows-7), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you