- Mikrotik minbox refused on wan how to#
- Mikrotik minbox refused on wan install#
- Mikrotik minbox refused on wan update#
- Mikrotik minbox refused on wan plus#
- Mikrotik minbox refused on wan mac#
Thank you for your reply, I really appreciate it. I have to change the WAN config, then it'll come back up - but only for 30 seconds.
Mikrotik minbox refused on wan plus#
Plus I do have internet access, just not for more than about 30 seconds. They're able to see on their end whether the router has connected, and they do. You're saying the router isn't connecting to the ISP's service? I know that it is. I am sure that you are not making a connection/IP address/MTU details with ISP and it's advice to check again. You're saying I should try connecting the CAT5 cable coming from the WISP's hardware to a POE switch, and then connecting that to the router's WAN port? Any reason you can think of that it'd work on other routers but not this Kumar wrote: The CAT5 runs from the antennae and radio on top of a tower outside our facility to the ground, in through the wall, where it connects into a POE injector that connects directly to the router.
Mikrotik minbox refused on wan how to#
How to Cisco router connected with your RF Connection? Is it directly connected to the RF device's cable where POE injector is connected? If then please try to connecting a switch middle of both device. I should add that the config on the C881 we're currently running matches the config that I'm using, with respect to the WAN configuration. I don't believe that these components are causing the issue.Īny help would be greatly appreciated. So the CAT5 cable runs from the antennae to the POE injector, which then plugs into our router. I've run cable tests on it and they've all passed. This is because that cable powers the radio equipment on a tower outside our facility.
Mikrotik minbox refused on wan install#
The only non-standard aspect to our install is that there's a POE injector on the WAN cable - the cable that would ordinarily be running from the ISP's modem to our router.
So we have an antennae and radio outside our facility. Our ISP is a WISP, or a fixed-based wireless provider. I'm replacing a Cisco C881 that we do not own and was only used as we used to be a branch office connected via a tunnel. Only the Cisco RV-series appears to have problems. But, so far, every other router I've tried works perfectly after configuring the static IP. It shipped with the second-to-latest release.
Mikrotik minbox refused on wan update#
Later still I grabbed a $50 Belkin Wireless Router we'd been using as a WAP and tried it - same thing, worked perfectly.ĭoes anyone have any suggestions I could try to make this work? The ONLY thing I haven't done is update the firmware. Configured it with the same Static IP I had been using, and it worked like a charm instantly. I've tried disabling the firewall in the router, but it makes no difference.įinally, in order to rule out the possibility that it was anything other than a router issue, I brought in a Ubiquiti EdgeRouter 4 that I have as an on-hand backup router. Nothing else is configured in the router - I'm literally powering it up, configuring WAN1, and then this happens. I tried configuring the connection when connected to WAN2, but same thing.įinally, I returned the RV345, thinking it may have been a hardware issue, and got a new RV340. No internet connectivity, though the router responded to LAN pings.
I could ping websites on the router or on a network device for about 20-30 seconds after re-configuring WAN1, but afterwards, nothing. They said it looked like it was connected on their end and could see that the router was sending traffic to an IP on AWS - I'm guessing this is a Cisco firmware update check. Finally I involved the ISP, and had them check things on their end. I did this many times, sometimes using DHCP, sometimes the Static IP settings. Machines on the network could connect to the internet, for about 30 seconds, after which no connectivity was available. Could resolve hostnames () and perform DNS lookups in the router's diagnostics area, but couldn't ping them. I powered up the RV345, logged in, changed the admin password, and set up WAN1 with the settings specified, and was shown in the WAN window that the connection was up on IPV4.
Mikrotik minbox refused on wan mac#
There is no MAC lock on the connection, as is sometimes the case with ISPs. We have a static IP, gateway, subnet, and DNS1 & DNS2 from our WISP, and the configuration is very simple - something I've setup many, many times in the past. We recently purchased an RV345 to use in our SMB setting.
0 kommentar(er)
