Pagina's: [1]

Auteur Topic: Synology DS213 + Belgacom  (gelezen 6439 keer)

Offline VJ DS213

  • Bedankjes
  • -Gegeven: 1
  • -Ontvangen: 0
  • Berichten: 2
Synology DS213 + Belgacom
« Gepost 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?

Offline malinwa001

  • Bedankjes
  • -Gegeven: 8
  • -Ontvangen: 2
  • Berichten: 69
Re: Synology DS213 + Belgacom
« Reactie #1 Gepost op: 07 mei 2013, 19:27:16 »
Bekijk even deze site :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
  • Mijn Synology: DS713+
  • HDD's: WD30EZRX

Offline dasuper

  • Bedankjes
  • -Gegeven: 1
  • -Ontvangen: 0
  • Berichten: 10
Re: Synology DS213 + Belgacom
« Reactie #2 Gepost 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?
  • Mijn Synology: ds213+

Offline Birdy

  • Global Moderator
  • MVP
  • *
  • Bedankjes
  • -Gegeven: 1346
  • -Ontvangen: 7841
  • Berichten: 43.383
  • Beter een muisarm dan een apestaartje
    • Truebase
Re: Synology DS213 + Belgacom
« Reactie #3 Gepost 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://userbase.be/forum/viewtopic.php?f=43&t=24487&start=0

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 ?


CS406      DSM 2.0-0731    DS508      DSM 4.0-2265      DS411+II  DSM 6.2.4-25556-7   DS115J    DSM 7.1.1-42962-5   DS918+    DSM 6.2.4-25556-7
DS107+     DSM 3.1-1639    DS411slim  DSM 6.2.4-25556   DS213J    DSM 6.2.3-25426-2   DS1515+   DSM 6.2.4-25556-7   DS220+    DSM 7.2.1-69057-5
DS107+     DSM 3.1-1639    DS111      DSM 5.2-5967-9    DS413J    DSM 6.2.3-25426-2   DS716+II  DSM 6.2.4-25556-7   RT2600ac  SRM 1.2.5-8227-11
BeeDrive   1TB             BeeServer  BSM 1.0-65162                                                                 MR2200ac  SRM 1.2.5-8227-11

Offline dasuper

  • Bedankjes
  • -Gegeven: 1
  • -Ontvangen: 0
  • Berichten: 10
Re: Synology DS213 + Belgacom
« Reactie #4 Gepost op: 29 september 2013, 15:09:07 »
ah , super daar ga ik vanavond mee aan de gang!

tx
  • Mijn Synology: ds213+

Offline dasuper

  • Bedankjes
  • -Gegeven: 1
  • -Ontvangen: 0
  • Berichten: 10
Re: Synology DS213 + Belgacom
« Reactie #5 Gepost 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!
  • Mijn Synology: ds213+

Offline adolfainsley8

  • Bedankjes
  • -Gegeven: 0
  • -Ontvangen: 0
  • Berichten: 1
Re: Synology DS213 + Belgacom
« Reactie #6 Gepost 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????

Online Robert Koopman

  • Global Moderator
  • MVP
  • *
  • Bedankjes
  • -Gegeven: 271
  • -Ontvangen: 1801
  • Berichten: 10.981
    • http://www.dwvbb.nl
Re: Synology DS213 + Belgacom
« Reactie #7 Gepost op: 26 april 2016, 09:11:34 »
Het is een draadje van 2,5 jaar geleden.
RS812+ : 3*WD60EFPX 6.2.4-25556 Update 7 SHR
RS814+ : 3*WD30EFRX 7.1.1-42962 Update 6 Btrfs

Offline Birdy

  • Global Moderator
  • MVP
  • *
  • Bedankjes
  • -Gegeven: 1346
  • -Ontvangen: 7841
  • Berichten: 43.383
  • Beter een muisarm dan een apestaartje
    • Truebase
Re: Synology DS213 + Belgacom
« Reactie #8 Gepost op: 26 april 2016, 09:15:34 »
Op slot gezet. ;)


CS406      DSM 2.0-0731    DS508      DSM 4.0-2265      DS411+II  DSM 6.2.4-25556-7   DS115J    DSM 7.1.1-42962-5   DS918+    DSM 6.2.4-25556-7
DS107+     DSM 3.1-1639    DS411slim  DSM 6.2.4-25556   DS213J    DSM 6.2.3-25426-2   DS1515+   DSM 6.2.4-25556-7   DS220+    DSM 7.2.1-69057-5
DS107+     DSM 3.1-1639    DS111      DSM 5.2-5967-9    DS413J    DSM 6.2.3-25426-2   DS716+II  DSM 6.2.4-25556-7   RT2600ac  SRM 1.2.5-8227-11
BeeDrive   1TB             BeeServer  BSM 1.0-65162                                                                 MR2200ac  SRM 1.2.5-8227-11
Pagina's: [1]
 

synology wel/niet oplossing voor ons, graag jullie hulp!

Gestart door denoBoard NAS hardware vragen

 Reacties: 2
Gelezen: 2449 		Laatste bericht 11 augustus 2009, 12:21:47
door Anonymous
Synology DS213air verschijnt niet in netwerk

Gestart door ScheepsjongenBoard NAS hardware vragen

 Reacties: 10
Gelezen: 3941 		Laatste bericht 06 augustus 2013, 19:32:34
door Scheepsjongen
Backup naar usb schijf op andere Synology NAS

Gestart door MarktBoard Data replicator & overige backupsoftware

 Reacties: 3
Gelezen: 1766 		Laatste bericht 19 februari 2015, 21:38:46
door Robert Koopman
Synology ziet 2 routers.

Gestart door Klikoo.Board DDNS / Quick Connect / EZ-Internet / Portforwarding

 Reacties: 24
Gelezen: 11956 		Laatste bericht 29 april 2015, 12:52:42
door Klikoo.
MusicIP op X86 Synology NAS

Gestart door B1tbullBoard Overige 3rd party packages

 Reacties: 4
Gelezen: 2842 		Laatste bericht 23 mei 2015, 19:00:30
door Grofweg