D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: nut4wine on April 25, 2011, 06:54:44 AM

Title: Why does 1.35NA Open a Port for BSecure
Post by: nut4wine on April 25, 2011, 06:54:44 AM

I recently upgraded my DIR-655, H/W Version A3 from 1.21 w/o SecureSpot to 1.35NA.  My understanding this that this version isn't supposed to have any SecureSpot support.  However, whenever the router is rebooted, the logs contain an entry that reads: 

Bsecure remote access enabled on port 8098.

I don't see any reason to allow this access but I see no way to disable it.  I suppose I can find a way to block it via some of the Advanced management features, but there's no guarantee that the built-in behavior wouldn't override any management changes I make.

Anyone have any insight into this issue?

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: FurryNutz on April 25, 2011, 07:58:24 AM

Maybe thats due to the fact that BSecure and SecureSpot are different things.
Any one on your network running a filtering program called BSecure?

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: marmoduke on April 25, 2011, 10:05:35 AM

Not so fast, Furry.

You may want to visit this page.  Bsecure was the engine for SecurreSpot.

http://www.bsecure.com/Offers/SecureSpot.aspx

As an aside, you may want to "reset factory defaults" and re-enter your settings manually.  If you used a backup of the settings file to restore your settings, there may be some legacy problem.

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: FurryNutz on April 25, 2011, 10:10:06 AM

Got there Duke...LOL. However someone could be running the SW version.

If not, then wonder why it's posting this in the logs if it's actually supposed to be gone from FW.  ???

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: marmoduke on April 25, 2011, 10:20:25 AM

Nut4:

Do you have a d-link NIC?  If so, remove the d-link wireless management software and use Microsoft product to control and manage your NIC connection.

Even if it doesn't cure the bsecure, it will guarantee more speed and less disconnects.

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: nut4wine on April 26, 2011, 04:10:23 AM

There's no one on the network running any version of SecureSpot.  I know I'm not and I'm the only one that manages the router.  I've never run SecureSpot or had any configuration information associated with it.  I don't see how anything inside my network could be affecting this change, they don't have the router's password.  There's never been anything in my logs about opening this port before, so I find it disconcerting for it to be there now. I know that if I subverted a router and opened a port for my own use, I'd put a message like that in the logs ;). 

D-Link technical support has been no help.  They suggest I call a "live technician".  That suggests a lack of knowledge about their own product.  Sigh.

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: FurryNutz on April 26, 2011, 07:05:00 AM

Is it effecting the router in anyway or connectivity?

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: davevt31 on April 26, 2011, 08:39:45 AM

Did you use a saved config file or manually enter your information after the flash?

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: nut4wine on April 27, 2011, 04:37:51 AM

It affects the router because there's a port open I don't want open.

I've seen the message after a factory reset and flash to the new firmware and after restoring configuration information.

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: davevt31 on April 27, 2011, 09:26:38 AM

Reflash but don't use the saved config, re-enter the settings manually.  The Besucure port opening is most likely coming from the saved config.  It is best when doing a major firmware update (1.2x -> 1.3x) to not used saved configs.  Its a little more work depending on the setup, but will cause less headaches.  After you get your settings done then save a new config file as you can reuse it with this version of the firmware if you need to reflash for some reason.

Title: Re: Why does 1.35NA Open a Port for BSecure
Post by: FurryNutz on April 27, 2011, 09:44:33 AM

Recommend the following FW update process:
1. Factory reset from the web page.
2. Update FW.
3. Factory reset once more.
4. Setup from scratch. Don't load any saved config file.

After you test for the port, if it's not there in the logs, then continue to set up and then save off a new config to file.