• February 27, 2025, 08:19:45 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: New Gateway Problem  (Read 4167 times)

ellacw

  • Level 1 Member
  • *
  • Posts: 7
New Gateway Problem
« on: October 02, 2010, 04:01:31 PM »
Switched from Bell to Rogers. Dlink is not seeing the internet/network. Old .. 2Wire Gateway to new SMC Networks SMCD3GN Gateway.. No ethernet or LAN activity indicated on front panel. Is there a potential issue in the firewall settings of the new Gateway? I would have suspected the DNS323 would have received the IP address fromthe gateway. I am lucky .. in that I still have the Bell service activated. I revitalized the DNS323 on Bell and confirmed it is still active and the DHCP client is disabled. For whatever reason when I try to engage through the SMC networks cable modem it is not recognized at all.
« Last Edit: October 02, 2010, 06:46:44 PM by ellacw »
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: New Gateway Problem
« Reply #1 on: October 02, 2010, 09:43:56 PM »
Quote from: ellacw on October 02, 2010, 04:01:31 PM
I am lucky .. in that I still have the Bell service activated. I revitalized the DNS323 on Bell and confirmed it is still active and the DHCP client is disabled. For whatever reason when I try to engage through the SMC networks cable modem it is not recognized at all.

The DHCP client is disabled - that is most likely the problem.

If you have the DNS-323's DHCP client disabled, you MUST ensure that the DNS-323's ip settings are suitable for the new router's addressing scheme.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

ellacw

  • Level 1 Member
  • *
  • Posts: 7
Re: New Gateway Problem
« Reply #2 on: October 03, 2010, 03:48:35 AM »
Thanks.. how to get at this is my struggle. I would have hoped after a reset of the DNS back to factory it would have been able to connect after receiving an IP address from the new SMC router. No go. I reverted back to the 2wire to enable change to static IP of Rogers .. was able to save .. the DNS still does not react and no ethernet connectivity is obtained. Advice on how to tackle this would be helpful. Cheers.
Logged

jamieburchell

  • Level 6 Member
  • *
  • Posts: 947
Re: New Gateway Problem
« Reply #3 on: October 03, 2010, 04:59:28 AM »
Just to confirm- you don't have a blue network light on constantly on the 323 when you connect to the new gateway?

Regardless of any DHCP settings, this light should be on when connected to a network I would have thought. Is it something silly like you need to turn the LAN ports on in the interface for your gateway, or perhaps try a different cable? Straight vs crossover? Although I would expect the 323 to auto negotiate that.
Logged
If your little 323 is not working right,
You've racked your brains and been up all night
Take a deep breath and wipe away the sweat,
Login as web admin and try a factory reset!

ellacw

  • Level 1 Member
  • *
  • Posts: 7
Re: New Gateway Problem
« Reply #4 on: October 03, 2010, 07:36:46 AM »
Well after some wonderful support from Tech 1 & 2 levels @ Dlink .. blame was pointed directly at the SMC gateway. The DNS network activity was sound. Good luck in trying to talk to SMC. I got it after going through the modem set-up before I chucked it on the lawn. There is conflict in LAN speed.For whatever reason AUTO speed is the issue. Default SMC LAN switch to 100mbps with no full duplex and you have it. Now time for a lovely fall ride on the bicycle. Cheers
Logged