Jump to content

Ade

Members
  • Content Count

    4
  • Joined

  • Last visited

Everything posted by Ade

  1. Hi, I'm hoping someone can help. I've been dragged into sorting an issue out, sadly the "full picture" is a bit hard to get, some I'm working with what I know: Theres a DM Sprite 2, connected to what I believe to be a BT Business Hub 5 with a Static IP. Everything previously worked okay, customer could remote in via a No-IP domain that was configured by the router. They had internet problems, BT replaced the router, nothing has worked since. I've reconfigured the No-IP redirect, reconfigured the sprite, it all works and can be accessed remotely. However, after about 5 minutes, the sprite has a tantrum, reboots, trying to access the device results in "Engineering Bootloader - No web server available", after about 10 minutes it starts working again and then the process repeats. Have swapped the sprite out for a brand new one, still happens, the only way we can stop it rebooting constantly is to isolate it from the internet, sadly it needs to be remote accessible. Any ideas? Pretty sure the DS2 is currently in the routers DMZ, should it be moved? What ports would work? Is this even fixable?
  2. Are we talking about the same recorder the DM Sprite 2 is over 12 years old. One option is your recorder collects its static local IP from router DMZ give the path through your router past firewall What happends when you do it manual Yeah another DM Sprite 2, he bought two at the same time, kept one in a cupboard. Tried manual IPs, Tried auto IPs. The problem isnt it collecting its local IPs (like I said, thats not related to DMZ is it? IP allocation is a DHCP thing) it always works until I try and open the whole thing to the internet at which point it all goes to hell.
  3. Are you sure? We're talking DMZ not DHCP? To be clear, the DS2 has a static IP, works perfectly fine within the network, items on the LAN can connect to it absolutely fine, can reboot both devices merrily and they continue to work. The sprite keeping the same internal IP every time. In order for it to be externally accessible from devices not on the LAN, I need to enable some form of external access via the router, so that requests to the external IP get routed to the correct internal IP (i.e. the sprite) as soon as I do that, it works, the outside world can get to it and I can view the cameras from any device on any network. However it then goes into the reboot issue mentioned above, which I'm lead to believe is due to the Sprite getting hammered by bots/port scanners. What I'm trying to work out is how to mitigate this, do I need to turn off DMZ and route specific external ports to the internal IP as opposed to the (I assume this is what the DMZ does) open season of all ports to that device. If so what ports? and would that fix this?
  4. Hi, sorry, perhaps having a stupid moment, can you elaborate on that? Until it went in the DMZ nothing could connect (I assume ports etc are blocked), if I take it back out of the DMZ then once again nothing can talk to it... Its an age since I've tried to set this kind of thing up
×