Synology-Forum.nl

Overige software => DDNS / Quick Connect / EZ-Internet / Portforwarding => Topic gestart door: VJ DS213 op 02 mei 2013, 18:24:08

Titel: Synology DS213 + Belgacom
Bericht door: VJ DS213 op 02 mei 2013, 18:24:08
Hoe benader je de NAS met een belgacom modem (bbox). Bij Port Forwarding verwijzen ze naar het tabblad NAT op de interface van de bbox, maar dat is helemaal niet meer te vinden.
Is een oplossing bv het plaatsen van een router achter de bbox? Maar hoe dan de instellingen zetten?
Titel: Re: Synology DS213 + Belgacom
Bericht door: malinwa001 op 07 mei 2013, 19:27:16
Bekijk even deze site :http://portforward.com/english/routers/port_forwarding/Belgacom/ (http://portforward.com/english/routers/port_forwarding/Belgacom/)
Kies de juiste router.

inloggen via 192.168.1.1
pasw staat op je router.

een voorbeeld om je telnetpoort open te zetten:

http://portforward.com/english/routers/port_forwarding/Belgacom/Fast3464/TELNET.htm (http://portforward.com/english/routers/port_forwarding/Belgacom/Fast3464/TELNET.htm)
Titel: Re: Synology DS213 + Belgacom
Bericht door: dasuper op 29 september 2013, 14:34:20
is het je uiteindelijk gelukt.. Ik zie het nog steeds niet... poort staat open, maar ik kan niet verbinden..

hieronder de log file...

Sep 29 14:28:09 2013   WBM Login   User authentication success    Username: user
Sep 29 14:22:42 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:55963->84.196.3.185:5005 on ppp0
Sep 29 14:22:42 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.10:55963->84.196.3.185:5005 on ppp0 [repeated 2 times, last time on Sep 29 14:22:42 2013]
Sep 29 14:21:18 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53325->17.172.232.104:5223 on ppp0
Sep 29 14:21:16 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53336->188.200.188.129:443 on ppp0
Sep 29 14:21:11 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53334->188.200.188.129:443 on ppp0
Sep 29 14:21:11 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53317->69.171.248.65:443 on ppp0
Sep 29 14:20:52 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0
Sep 29 14:19:22 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.4:59849->199.47.218.159:443 on ppp0
Sep 29 14:18:20 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:56299->194.78.99.24:80 on ppp0
Sep 29 14:16:39 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:56228->174.35.64.50:80 on ppp0
Sep 29 14:16:38 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.2:57349->173.252.103.16:443 on ppp0
Sep 29 14:15:30 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:56120->174.35.67.54:80 on ppp0
Sep 29 14:13:25 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.7:52417->188.200.188.129:443 on ppp0
Sep 29 14:13:25 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.7:52417->188.200.188.129:443 on ppp0
Sep 29 14:12:42 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:55883->84.196.3.185:5005 on ppp0
Sep 29 14:12:42 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.10:55883->84.196.3.185:5005 on ppp0 [repeated 2 times, last time on Sep 29 14:12:42 2013]
Sep 29 14:12:03 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53326->188.200.188.129:443 on ppp0
Sep 29 14:11:14 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:55308->84.196.3.185:5005 on ppp0
Sep 29 14:11:14 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.10:55308->84.196.3.185:5005 on ppp0 [repeated 2 times, last time on Sep 29 14:11:14 2013]
Sep 29 14:08:23 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.2:57348->173.252.103.16:443 on ppp0 [repeated 2 times, last time on Sep 29 14:08:23 2013]
Sep 29 14:06:24 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.5:50875->17.172.232.221:5223 on ppp0
Sep 29 14:06:17 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.5:50875->17.172.232.221:5223 on ppp0
Sep 29 14:06:14 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0
Sep 29 14:06:04 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.5:50875->17.172.232.221:5223 on ppp0 [repeated 6 times, last time on Sep 29 14:06:13 2013]
Sep 29 14:04:51 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53316->17.172.232.79:5223 on ppp0
Sep 29 14:04:03 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:54236->173.194.67.103:80 on ppp0
Sep 29 14:04:03 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:35560->173.194.41.186:80 on ppp0
Sep 29 14:02:50 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:55194->194.78.100.26:80 on ppp0
Sep 29 14:01:44 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:47155->108.160.165.253:443 on ppp0
Sep 29 14:01:43 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:54603->107.22.180.95:443 on ppp0
Sep 29 13:59:23 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.2:57336->188.200.188.129:443 on ppp0
Sep 29 13:59:23 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.2:57336->188.200.188.129:443 on ppp0
Sep 29 13:59:20 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.2:57337->69.171.235.48:443 on ppp0
Sep 29 13:58:05 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:60376->69.171.235.48:443 on ppp0
Sep 29 13:56:53 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:54822->194.78.100.26:80 on ppp0
Sep 29 13:54:58 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.2:57337->69.171.235.48:443 on ppp0 [repeated 3 times, last time on Sep 29 13:55:08 2013]
Sep 29 13:54:56 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.2:57334->194.78.0.148:443 on ppp0 [repeated 2 times, last time on Sep 29 13:54:56 2013]
Sep 29 13:54:53 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.2:57337->69.171.235.48:443 on ppp0 [repeated 3 times, last time on Sep 29 13:54:55 2013]
Sep 29 13:53:05 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.10:54695->84.196.3.185:6690 on ppp0
Sep 29 13:52:23 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53291->194.78.100.32:80 on ppp0
Sep 29 13:52:14 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53280->17.149.36.78:5223 on ppp0
Sep 29 13:51:47 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0
Sep 29 13:51:46 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.3:56995->17.149.36.189:443 on ppp0
Sep 29 13:51:42 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56995->17.149.36.189:443 on ppp0
Sep 29 13:51:38 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0
Sep 29 13:51:31 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56995->17.149.36.189:443 on ppp0 [repeated 2 times, last time on Sep 29 13:51:35 2013]
Sep 29 13:51:31 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0
Sep 29 13:51:27 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56995->17.149.36.189:443 on ppp0 [repeated 3 times, last time on Sep 29 13:51:28 2013]
Sep 29 13:51:22 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.3:56993->69.171.235.48:443 on ppp0 [repeated 4 times, last time on Sep 29 13:51:27 2013]
Sep 29 13:50:20 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:56725->69.171.248.65:443 on ppp0
Sep 29 13:48:59 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.6:56725->69.171.248.65:443 on ppp0 [repeated 4 times, last time on Sep 29 13:49:11 2013]
Sep 29 13:47:23 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:44269->173.194.78.188:5228 on ppp0
Sep 29 13:47:14 2013   Outbound Traffic   Blocked - NAT out failed   ICMP type 3 code 1 91.183.224.101->173.194.78.188 on ppp0
Sep 29 13:47:11 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.6:44269->173.194.78.188:5228 on ppp0
Sep 29 13:46:03 2013   Outbound Traffic   Blocked - NAT out failed   Packet not in tcp window: TCP 192.168.1.6:44269->173.194.78.188:5228 on ppp0 [repeated 3 times, last time on Sep 29 13:46:42 2013]
Sep 29 13:43:16 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.4:59717->74.125.195.106:80 on ppp0
Sep 29 13:43:16 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.4:59718->74.125.195.94:80 on ppp0
Sep 29 13:43:16 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.4:59719->23.77.114.16:80 on ppp0
Sep 29 13:43:08 2013   Outbound Traffic   Blocked - NAT out failed   First packet in connection is not a SYN packet: TCP 192.168.1.9:53275->69.171.235.48:443 on ppp0



iemand enig idee hoe ik dit voor elkaar kan krijgen?
Titel: Re: Synology DS213 + Belgacom
Bericht door: Birdy op 29 september 2013, 14:52:00
Even geGoogled op: Outbound Traffic Blocked - NAT out failed First packet in connection is not a SYN packet
Gevonden:

http://www.walterdevos.be/bbox2-sagem-blocked-nat-out-failed-first-packet-in-connection-is-not-a-syn-packet (http://www.walterdevos.be/bbox2-sagem-blocked-nat-out-failed-first-packet-in-connection-is-not-a-syn-packet)

http://userbase.be/forum/viewtopic.php?f=43&t=24487&start=0 (http://userbase.be/forum/viewtopic.php?f=43&t=24487&start=0)

http://forums.boxee.tv/printthread.php?t=64349&pp=10 (http://forums.boxee.tv/printthread.php?t=64349&pp=10)

En zo zijn er nog een aantal hits, dus, even Google gebruiken.

Kan je daar soms wat mee ?
Titel: Re: Synology DS213 + Belgacom
Bericht door: dasuper op 29 september 2013, 15:09:07
ah , super daar ga ik vanavond mee aan de gang!

tx
Titel: Re: Synology DS213 + Belgacom
Bericht door: dasuper op 29 september 2013, 16:11:22
@Birdy

vreemd genoeg werkt het wel als ik bij mij thuis vandaan probeer in teloggen (telenet), alleen op locatie op het interne netwerk van belgacom lukt het niet om buitenom te gaan. Dit is toch vreemd vind ik aangezien bij mij thuis op het telenet netwerk het wel lukt om via het interne netwerk van telenet buitenom op mijn nas te komen..

cheers, en nogmaals bedankt voor je snelle reactie!
Titel: Re: Synology DS213 + Belgacom
Bericht door: adolfainsley8 op 26 april 2016, 08:09:46
Dit is toch vreemd vind ik aangezien bij mij thuis op het telenet netwerk het wel lukt om via het interne netwerk van telenet buitenom op mijn nas te komen????
Titel: Re: Synology DS213 + Belgacom
Bericht door: Robert Koopman op 26 april 2016, 09:11:34
Het is een draadje van 2,5 jaar geleden.
Titel: Re: Synology DS213 + Belgacom
Bericht door: Birdy op 26 april 2016, 09:15:34
Op slot gezet. ;)