What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

New BE-98 Pro

Lotta Cox

Senior Member
I just setup a BE98 Pro. Stock updated firmware. The only issue was some, not all of iOT devices did not connect to 2.4.
I used guest network pro and created an iOT network called Idiots under the original SSID for 2.4. As soon as I did that all of the 2.4 iOT devices that did not connect previously connect, connected instantly. Is this the correct method? It's 100% stable now.

The only thing that did not connect is a RT AC 68U that is in Media Bridge mode. I don't see it in the Asus Discovery app anymore. Not in the client list either. Rebooted it, didn't help.
How can I get that 68U reconnected again?
 
The primary point in the IoT guest network is not for isolation, it's for compatibility. The default wireless settings for the IoT network are designed to be as widely compatible with cheap IoT wireless modules as possible.
 
I get what you're saying, but doesn't it achieve the result of isolating those devices from your main network? That's the main reason I'm using the IoT Network on my BT10 's. I see a lot of complaints about the Asus Zen Wi-Fi routers, but this mesh unit has been solid.
 
I get what you're saying, but doesn't it achieve the result of isolating those devices from your main network? That's the main reason I'm using the IoT Network on my BT10 's. I see a lot of complaints about the Asus Zen Wi-Fi routers, but this mesh unit has been solid.
No. The default IoT network is on the same VLAN as the main network. The reason being, quite a few IoT devices need to be able to talk with you over wifi, with your smartphone for example. So the default is having things on the same VLAN.

If you need isolation, you need to configure a separate network on a different VLAN.
 
I can't access 2 separate USB hard drives in windows with this 98 pro. Both are listed in the Samba place and network map.
But in windows explorer, I can only ever access the first drive that is plugged in. I can't find anyway to access the 2nd plugged in drive.
Works in every other router I've had.
What is wrong?

iHqPNps.png

5MZorxJ.png

YqTsehV.png
 
No. The default IoT network is on the same VLAN as the main network. The reason being, quite a few IoT devices need to be able to talk with you over wifi, with your smartphone for example. So the default is having things on the same VLAN.

If you need isolation, you need to configure a separate network on a different VLAN.
I see, something else i will research on how to do. Thanks
 
Last edited:
Samba seems so different on the 98 pro. I can't copy files to the attached hard drive. IDK how to change permissions. Just seems bugged or something.
Would installing Merlin's FW on this make USB server work like previous routers?
I had to plug my drives into my 68U. So easy to use there. Just like my ax86U.
Would rather have them attached to the 98pro.
 
Last edited:
@ColinTaylor Yes i can but I can not copy files or folder to the root of that drive where all the files and folder are now. I can copy a file or folder from that root to a PC.
I can go into any folder and write to it.
This is not how it worked before. Plus, I can't access a second HD attached at all.
 
@ColinTaylor Yes i can but I can not copy files or folder to the root of that drive where all the files and folder are now. I can copy a file or folder from that root to a PC.
I can go into any folder and write to it.
That's always how it's worked in my experience. You have to create folders (shares) in the root of the drive by clicking on the + icon (on the top right) and then assign user permissions to each share. You cannot write to the root unless you turn on "Allow guest login", in which case there are no individual shared folders as the whole drive (including the root) is writable by everyone.
 
That's always how it's worked in my experience. You have to create folders (shares) in the root of the drive by clicking on the + icon (on the top right) and then assign user permissions to each share. You cannot write to the root unless you turn on "Allow guest login", in which case there are no individual shared folders as the whole drive (including the root) is writable by everyone.
@ColinTaylor Good call! I can access both drive with guest enabled too :D THX!
I always used guest previously.
But .. some of my other PC's can't access the drives with guest mode enabled. Windows say can't access this drive. Is there some network settings in windows that might make it work? Like public or private network thingy or something? IDK
 
But .. some of my other PC's can't access the drives with guest mode enabled. Windows say can't access this drive. Is there some network settings in windows that might make it work? Like public or private network thingy or something? IDK
Guest access has long (25+ years) been depreciated by Microsoft and each successive Windows update seems to make it more difficult to reenable it (using registry hacks). Google to see if/what the current workarounds are for your particular PCs.

 
Guest access has long (25+ years) been depreciated by Microsoft and each successive Windows update seems to make it more difficult to reenable it (using registry hacks). Google to see if/what the current workarounds are for your particular PCs.

U ROCK! 🎸 🎸🎸
I followed this part in that guide:

TY so much man!
Happy VD
💕

6. Disable the SMB client signing requirement:

a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step 8.

b. In the console tree, select Computer Configuration > Windows Settings > Security Settings> Local Policies > Security Options.

c. Double-click Microsoft network client: Digitally sign communications (always).

d. Select Disabled > OK.



7. Disable the guest fallback protection:

a. On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor). If you are using Home edition, skip to step e.

b. In the console tree, select Computer Configuration > Administrative Templates> Network > Lanman Workstation.

c. Double-click Enable insecure guest logons

d. Select Enabled > OK.
 
Merlin firmware doesn't improve nothing on for 📶. If most or your clients are IoTs on the single 2.4GHz radio - we may see you again soon. This is the major complaint around Wi-Fi 7 products and not limited to Asus models. You also need to know AiMesh compatibility between 3006.102, 3004.388 and 3004.386 devices is still gray area and what Asus advertises for AiMesh is not exactly true in many cases. Keep your old routers around for some time. Good luck!
 
Last edited:
Xx8sAqa.png

Merlin firmware doesn't improve nothing on for 📶. If most or your clients are IoTs on the single 2.4GHz radio - we may see you again soon. This is the major complaint around Wi-Fi 7 products and not limited to Asus models. You also need to know AiMesh compatibility between 3006.102, 3004.388 and 3004.386 devices is still gray area and what Asus advertises for AiMesh is not exactly true in many cases. Keep your old routers around for some time. Good luck!
I know it does not improve signal. Never said it did.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top