New answers tagged connection
Ok, It was strange, i've started the service from services.msc, that showed me that the service is running, but in fact, it was not.. By task manager, the service xinetServer was offline. SO i've started it and everithing seems to be good, even the [.132] ---> [.132] who i suspected the firewall, but who did not pass the windows firewall effectively.
I have solved the problem myself, in the end it was not a Samba problem at all, but a Windows problem. The solution was to add a batch file that sets the credentials for netenab when Windows boots. The batch file contains: net use \\netenab\kie /user:wildfly wildfly And i needed to place it into C:\Users[USER]\AppData\Roaming\Microsoft\Windows\Start ...
This worked for me: service screen restart I believe our server just had too many tty sessions running (which screen sessions actually are) and couln't create a new one. We've had this problem only once before and we had about the same size of screens running. After finding the bug, we also reinstalled "screen" by typing: apt-get purge screen apt-get ...
Those are most certainly failed connection attempts. Check out with tcpdump; you should see them along with your host's ICMP port unreachable (since you don't have anything listening on that port): 01:58:31.471535 IP some.remote.host.24053 > your.local.host.21095: UDP, length 35 01:58:31.472006 IP your.local.host > some.remote.host: ICMP ...
Top 50 recent answers are included