Page 1 of 1

Cannot connect to 192.168.88.1 in setup

Posted: Fri Jan 19, 2018 11:56 am
by odonaghue
Hi,
I recently received the SXT LTE product but my PC does not recognize the hardware when I follow the prompt to access it at 192.168.88.1.
I have tried a few different cables and all are working fine, is there anything else I can check.
Or is the unit possibly faulty?

Regards
Adrian.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Fri Jan 19, 2018 12:00 pm
by jarda
Most probably your pc is in other ip address range. Use mac address instead to connect by winbox and set the ip parameters according to the rest of your network.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Fri Jan 19, 2018 1:22 pm
by odonaghue
Tried connecting in winbox using the mac.......
No success, showing connection to Mac address but displaying..... Error: could not connect to .......

Re: Cannot connect to 192.168.88.1 in setup

Posted: Fri Jan 19, 2018 1:42 pm
by jarda
Put the wire directly, switch off firewall, antivirus and run winbox as administrator. Reset the device and try again.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Fri Jan 19, 2018 1:43 pm
by jarda
Disabling other network adapters in Windows could help also in some cases.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Sat Jan 20, 2018 1:46 pm
by odonaghue
Hi, I tried all of the actions listed but to no avail. The unit is powering up ok and there seems to be an Ethernet signal going to the unit, but the PC cannot communicate in any way.
I have also tried to connect using the MAC address instead of the IP address in Winbox. Could the unit be faulty in some way, I only bought it last week.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Sat Jan 20, 2018 3:04 pm
by jarda
Either it is faulty or you have something badly set in your pc. Or both. Those advices work if followed properly. You can also try to put a switch between your pc and the device.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Sat Jan 20, 2018 4:27 pm
by acruhl
I would be very surprised if there was a problem with the device.

Another thing to try is if you have another MikroTik, connect it to that and do /tool mac-telnet <MAC> from the other one and see what happens. All this talk of disabling firewalls and other interfaces on Windows seems too complicated to make something simple like this work.

Re: Cannot connect to 192.168.88.1 in setup

Posted: Sun Jan 21, 2018 4:16 pm
by odonaghue
Success!!!! I'm unsure what I done, I think that I reset the device and reset the LAN connection at the same time but I have got it fully connected now. Thanks all for your support on this. Works a treat.
One more question......what device do I need now to deliver the signal wirelessly? Wireless router? Is it possible to use the wireless router that was supplied by the Internet provider? Bridged connection or something?

Re: Cannot connect to 192.168.88.1 in setup

Posted: Sun Jan 21, 2018 5:23 pm
by acruhl
Usually anything that is doing WiFi that is bridged to real ethernet ports (meaning almost any home "router") can work as a WiFi access point. The only warning is that you can "brick" it while changing the IP addressing if you're not careful. And you need IP addressing to be able to change the WiFi SSID and password... Probably you would just have to return it to factory settings to "unbrick" and try again...

So if your MikroTik lan is 192.168.88.0/24 by default, your WiFi router would need an address in that space plus a default route to 192.168.88.1. Some routers don't want to be a dhcp client on the "LAN" side, so you would have to set it statically. If you can do this, it will work fine. Some routers have an "AP mode" that might work as well. I have an ASUS router that does this and automatically turns the AP into a DHCP client on all wired ports so it's really easy.

My recommendation - Just get another MikroTik. You can get a really nice one with good range for less than $100, or you can get like a hAP-mini or lite, or mAP-lite or cAP-lite shipped to you for less than $30 (or maybe $40 for mAP and cAP). How can you beat that? And you can configure the "other" device using mac-telnet so you can't "brick" it.