Stop Discovery from SMC

Smc Smc smcwbr14-g2 barricade g 2.4ghz...
April 13, 2010 at 20:57:21
Specs: Windows 7
Is there any way to stop the router from trying to get a ADSL connection?

2010-04-13 04:54:40 DHCP Client: Could not find DHCP daemon to get information
2010-04-13 04:54:35 DHCP Client: Send Discover
2010-04-13 04:54:30 DHCP Client: Send Discover
2010-04-13 04:54:25 DHCP Client: Send Discover
2010-04-13 04:54:20 DHCP Client: Send Discover
2010-04-13 04:54:15 DHCP Client: Send Discover
2010-04-13 04:54:15 DHCP Client: Could not find DHCP daemon to get information

SMC does not have the option to configure the router to different modes like d-link, cisco and many others do!... pretty dumb IMHO.

Is There a way to change this?

See More: Stop Discovery from SMC

Report •

April 14, 2010 at 07:49:28
So I'm guessing this router isn't connected to the internet and these discover requests are on the WAN side of it?

If that's the case, I'm not sure what your issue is. The requests aren't anything that's going to rob you, or connected clients of bandwidth.

Report •

April 14, 2010 at 13:43:15
Yes that is correct. The issue is that the constant discovery attempts gets logged and the system is recurrently trying to do something it should not. It's like having a rogue process running on your system, it uses resources and can cause crashes.

However i have found a fix. I set a static IP and it stops from trying to do discovery. Still it's a huge flaw on SMC side not to have diff operation modes for this router as they have for higher end models, and as many other brands also do.

Report •

April 15, 2010 at 07:50:33
Well, I don't know that it's a flaw.

Simply put, the discover requests don't use up enough bandwidth to interfere with LAN clients communication.

So the only real issue at hand is the fact that "the constant discovery attempts gets logged" which can be circumvented easily but either shutting off logging, or if that's not possible, just stop reading the logs.

it's like having a rogue process running on your system, it uses resources and can cause crashes.

I suspect you're letting a very little thing cause you more irritation than it's worth.

It's not likely to cause a crash. The NIC on your PC, while connected to a network, constantly sends out requests for connectivity. Which is to say, while sitting idle, it sends out a packet saying, "Hello I'm here, is there anybody out there" and it then in turn gets a reply. This is done to verify connectivity, nothing more. Does this cause crashes? No.

You're worrying about nothing. Let it go, take a deep breath and relax. The sky is not going to fall if you can't shut off the DHCP discover request.

Report •

Related Solutions

April 15, 2010 at 11:02:23
Actually it was crashing every 20 mins, but with the fixed ip setting it has been running smoothly. That and using the forever setting in the main routers DHCP settings.

Report •

April 15, 2010 at 12:40:55
Not to pick at nits but, you said, "it uses resources and can cause crashes." which is not the same thing as, "Actually it was crashing every 20 mins".

Just for future reference, should you have issues that cause you to come to a tech help site like this again, you want to post all pertinent information. I double checked just to keep my foot out of my mouth and sure enough, no mention of the unit crashing other than what I copied and pasted above.

Had we known it was crashing, we would have probably taken a different troubleshooting track (or at least, I would have) instead of the one we did.

Having said that....

I've never worked with any SMC. For the most part, I do enterprise level networking here at work. However, we do run an in-house wireless network that provides nothing but internet access and is unsecured. Call it a "guest wireless network". For that we are presently using SOHO level equipment. We do have plans for an enterprise level in-house wireless network that will be able to provide secure access to internal resources as well as external "guest" type access for non-employees. However, due to the present economic situation, that's been pushed back until we have the budget for it.

So far I've used a lot of D-Link equipment but I found it breaks down too quickly. As a result, we've settled on Linksys WRT54GL routers running tomato firmware. I like them a lot and so far I haven't had a single one break. The third party firmware gives a lot of additional features not available on the default firmware and, it's linux based.

All of the aforementioned Linksys routers are being used as Access Points with one exception. Therefore none of them have the WAN port in use. I didn't have to disable anything or fake any IP's on the WAN side in order to prevent discovery packets being sent out. Because that port isn't in used, technically, it's disabled and there are no records of discovery requests, or any other kind, going out on the WAN side.

You may want to consider getting rid of the SMC router and buying yourself something a little better.

Also, it could very well be there is a hardware malfunction in your unit causing it to crash. Discovery packets in and of themselves won't make your system crash. But if is a hardware issue, then you most definitely want to replace the unit.

Report •

Ask Question