Connection via VPN was working then wasn’t

Forums / NoMachine for Windows / Connection via VPN was working then wasn’t

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #31436
    AvatarRadioFred
    Participant

    client _6.10.12._1

    Windows 10 home

    server _6.9.2.1

    Windows 10 pro

     

    connectivity was working, and then stopped working;

    “Could not connect to the server.

    Error is 108: Connection reset by peer”

    \documents\nomachine\….01202021…

    1/20/21

    wnhn@wnhn-OptiPlex-GX260:~$ sudo tcpdump -i eth0 host 192.168.50.40

    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

    listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes

    09:08:08.737445 IP 192.168.50.40.17500 > 255.255.255.255.17500: UDP, length 373

    09:08:08.737834 IP 192.168.50.40.17500 > 192.168.50.255.17500: UDP, length 373

    09:08:16.376156 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [S], seq 1184888491, win 64240, options [mss 1358,nop,wscale 8,nop,nop,sackOK], length 0

    09:08:16.376911 IP 192.168.50.40.4000 > 10.8.0.14.50679: Flags [S.], seq 3946745519, ack 1184888492, win 65535, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

    09:08:16.468448 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [.], ack 1, win 1029, length 0

    09:08:16.469910 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:16.770572 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:17.111495 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:17.712031 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:18.913257 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:20.113998 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:21.314205 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:21.386693 ARP, Request who-has 192.168.50.40 tell 192.168.50.30, length 28

    09:08:21.386873 ARP, Reply 192.168.50.40 is-at c8:1f:66:02:1f:06 (oui Unknown), length 46

    09:08:23.714509 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:28.514803 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [P.], seq 1:13, ack 1, win 1029, length 12

    09:08:38.114855 IP 10.8.0.14.50679 > 192.168.50.40.4000: Flags [R.], seq 13, ack 1, win 0, length 0

    09:08:38.765684 IP 192.168.50.40.17500 > 255.255.255.255.17500: UDP, length 373

    09:08:38.766275 IP 192.168.50.40.17500 > 192.168.50.255.17500: UDP, length 373

    09:09:08.786460 IP 192.168.50.40.17500 > 255.255.255.255.17500: UDP, length 373

    09:09:08.787146 IP 192.168.50.40.17500 > 192.168.50.255.17500: UDP, length 373

    21 packets captured

    21 packets received by filter

    0 packets dropped by kernel

    wnhn@wnhn-OptiPlex-GX260:~$

    Attachments:
    #31588
    AvatarCarin
    Participant

    Hi RadioFred,

    Can you please send us logs from both client and server sides. From the server side we need debug logs. We will need you to enable debug, restart nxserver and then reproduce the issue and collect the logs.

    You can see the following article for guidance: https://www.nomachine.com/DT11R00181&dn=logs#1.4.

    Please send them directly to us via email to forum[at]nomachine[dot]com and we will take a look. Please use the title of this topic as the subject of your email. Thanks!

     

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.