New Dell PC can't access D-Link router configuration page

[zl79111]

Why would you do that? There was no reason to disconnect
the router and plug the new PC into the modem. Does NTL use
the mac address of the computer for connection purposes? If
so, when did you change the mac address and does it need
changed back?

***As I can't accessed internet, I called NTL support who suggested
connection to modem directly. Then accessing the configuration page to
add new pc name. Nothing else done.

This looks incorrect. I assume you mean you set these
addresses on the new computer, not the router.

*** You are right.
Is the

router set to 192.168.0.1 on it's LAN, not WAN port? *** Both.

Can you ping the router from the new Dell system?

*** Ping 192.168.0.1 got time out message.

You might want to temporarily disable the (winXPSP2?)
firewall on the Dell system.

*** Could suggest how to disable the winXPSP2 ? SP2 is used for this XP
media centre.

The DNS server address should be set to your ISP's DNS
server if you aren't sure the router has DNS caching/serving
functionality. Normally, a typical setup would be to have
the router's DHCP set to automatically pass all the above
info to the Dell PC when it boots windows, including the DNS
addresses. When you choose to manually configure these
things, you need the DNS addresses for NTL (which the router
may list on it's browser config screens somewhere).

*** Now using DHCP. ipconfig can see all the parameter OK.
But still get time out when ping 192.168.0.1.

If the pinging of the router from the Dell PC works, next
try entering in an address on the internet, for a ping, or
in a browser if it's a website. The browser may note a DNS
problem in it's info panel (at the bottom)?




Is this still using wired, or wireless? Since it's in this
state you can disregard the suggestion above to try pinging
the router, obviously it starts to connect to it. Make sure
the firewall on the PC is disabled for the time being.

The new pc is always wired. The other 2 pcs are wireless. Window
firewall was disabled. I can see this new pcname and mac address from a
working pc in the page of DHCP of router. But can't ping the router.

Do you "need" to have static configuration of this new PC?
If not, is the router's DHCP function enabled? I suggest
you ought to try that, have the router DHCP feature enabled
and set the Dell system to "Obtain address... automatically"
in the TCP/IP properties for this network adapter. *** Done.

At that point, have the firewall disabled and try pinging
the router again. Just for the heck of it, try a different
network cable too.

*** replaced the new pc with a laptop and it worked ok.

 

[zl79111]

You are right and now the dhcp is used. I have no ZoneAlarm.

 

[kony]

NTL configuration page was accessed via the modem box. only to add new
PC number. No installation program was installed.

?

What does "add new PC number" mean?

You should not have need to do anything with NTL regarding
your new system. As far as your ISP is concerned, your
router is the only "PC". As far as your systems are
concerned, your router is the *ISP* (in the only necessary
sense, this is only a loose working relationship).


If NTL now considered your new PC's mac address as the mac
assigned to the account, you need to go back and register
the router, not a PC.

 

[kony]

***As I can't accessed internet, I called NTL support who suggested
connection to modem directly. Then accessing the configuration page to
add new pc name. Nothing else done.

This is their "we don't care what your actual problem is,
only that our ISP service works as advertised", approach to
troubleshooting... and that's not unexpected, ISPs don't
generally support routers unless it was equipment they
provided. While not unexpected, it doesn't solve your
problem and may result in things that need UNdone.

*** You are right.
Is the
*** Both.

Why? I mean, no that is incorrect.
Assuming your account does not have a static IP address
assigned (which it might, if this is a feature your ISP
expressly advertised and/or your particular account has this
premium, often paid-for additional feature), it is not
supposed to have a fixed WAN address, that is assigned to
your router when it gets IT'S DHCP info from the ISP's
router.

Your router's LAN address does need set manually (or left to
the default the router manufacturer set it to, which appears
to be 192.168.0.1, and if fine left at that address.

*** Ping 192.168.0.1 got time out message.

Open a command prompt and type "ipconfig /all"
and see if your system has a correct IP address, subnet
mask, a default gateway that is same as the router's LAN IP
address (which again appears to be 192.168.0.1 ??)

You might also ping that system from itself. For example if
it's IP address were 192.168.0.110, "ping 192.168.0.110"

*** Could suggest how to disable the winXPSP2 ? SP2 is used for this XP
media centre.

No, disable the firewall, not disable a service pack itself.
It is a setting in the security center.

http://www.utmem.edu/helpdesk/sp2/sp2firewall.htm

*** Now using DHCP. ipconfig can see all the parameter OK.
But still get time out when ping 192.168.0.1.

What does "ipconfig can see... ok" mean? Are the settings
correct?
Does your network adapter and router (Or if a switch
inbetween these, then it) have the connection LEDs lit?

The new pc is always wired. The other 2 pcs are wireless. Window
firewall was disabled. I can see this new pcname and mac address from a
working pc in the page of DHCP of router. But can't ping the router.

Does you router have a setting to disregard pings, perhaps
this is enabled (enabled meaning, disregard them)?
What happens if you try to ping another system, on your lan,
and one on the internet?

 

[zl79111]

This is their "we don't care what your actual problem is,
only that our ISP service works as advertised", approach to
troubleshooting... and that's not unexpected, ISPs don't
generally support routers unless it was equipment they
provided. While not unexpected, it doesn't solve your
problem and may result in things that need UNdone.

/ NTL suggested the following done:
to add new pc name
to type in NTL PID
to type in NTL PWD
to type ncpa.cpl in run-cmd mode.

From the router status I write down the wan Mac address. For the new

pc, under the ipconfig /all, the physical address of ethernet adapter
local area connection is the same as the wan Mac address. For other
working pc, these two addresses are different. Does this mean
something?
/

Why? I mean, no that is incorrect.

/ Sorry. 192.168.0.1 on LAN, not WAN
/

Assuming your account does not have a static IP address
assigned (which it might, if this is a feature your ISP
expressly advertised and/or your particular account has this
premium, often paid-for additional feature), it is not
supposed to have a fixed WAN address, that is assigned to
your router when it gets IT'S DHCP info from the ISP's
router.

Your router's LAN address does need set manually (or left to
the default the router manufacturer set it to, which appears
to be 192.168.0.1, and if fine left at that address.




Open a command prompt and type "ipconfig /all"
and see if your system has a correct IP address, subnet
mask, a default gateway that is same as the router's LAN IP
address (which again appears to be 192.168.0.1 ??)

/ Yes, all correct.
/

You might also ping that system from itself. For example if
it's IP address were 192.168.0.110, "ping 192.168.0.110"

/ new pc can ping itself. 192.168.0.102.

No, disable the firewall, not disable a service pack itself.
It is a setting in the security center.

/The window firewall was off.
/

http://www.utmem.edu/helpdesk/sp2/sp2firewall.htm



What does "ipconfig can see... ok" mean? Are the settings
correct?

/ Yes
/

Does your network adapter and router (Or if a switch
inbetween these, then it) have the connection LEDs lit?

/ Yes, connection OK
/

Does you router have a setting to disregard pings, perhaps
this is enabled (enabled meaning, disregard them)?

/ under Block WAN Ping
When you "Block WAN Ping", you are causing the public WAN IP address on
the DI-624+ to not respond to ping commands. Pinging public WAN IP
addresses is a common method used by hackers to test whether your WAN
IP address is valid.

Discard PING from WAN side: Disabled

What happens if you try to ping another system, on your lan,
and one on the internet?

/in run-cmd mode:
New pc can only ping itself. Can't ping router or other working pcs.
Working pc No.1 can ping working pc No.2.
Working pc No.1 can't ping New Pc.

 

[jaster]

You are right and now the dhcp is used. I have no ZoneAlarm.

Hmm, I question 83 transmitted 8 received, check again.

Since the router's DHCP gave you an IP address, you're connected to the
router. Again since the other machines see that pc (192.x.x.102 laptop's
?) DHCP address on the router the PC is connected to the router.
I also assume you can surf through the router?

This leaves the question why ping the router isn't working.

Usually, that means a firewall on the router or PC is blocking ICMP
packets. As kony suggests you should ping localhost, 127.0.0.1 and
the DHCP assigned IP address just to make sure ping is working.
You can also try ping www.yahoo.com, etc to test internet pings.

Sometimes a router can be set to block ICMPs (pings and tracerts). But
since the wireless pcs can ping the router I can't imagine the router
blocking wired pings while allowing wireless pings. I could be wrong but
at best I think it'd go the other way around, ie, allow wired but not
wireless.

Setting Windows Firewall to default settings usually clears up local
machine blocks but with your issue disable the Firewall then a
good ping would confirm it was Windows firewall. Ditto

 

[kony]

/ NTL suggested the following done:
to add new pc name
to type in NTL PID
to type in NTL PWD
to type ncpa.cpl in run-cmd mode.

I need for you to provide complete information, what is
written above is not enough and this can't be solved if you
don't henceforth write complete info- otherwise it will
leave us guessing. What I mean it, you write down the wan
mac address of what, the router? It seems that is what you
meant, but it doesn't seem to make sense because you should
not need a written copy of your router's WAN address for
anything.

For the new
pc, under the ipconfig /all, the physical address of ethernet adapter
local area connection is the same as the wan Mac address.

Are you sure you aren't confusing terms?
The MAC WAN IP address is the address assigned to the port
that connects to the modem. The router LAN IP address is
the one connecting to the switch in the router (if it has
one), seen by the other systems on the LAN as the gateway IP
address.

Whatever it is that you have done, undo it.
Get the router back to the way it started before any of
this. Get the ISP config info back to the way it was before
any of this. Get the new Dell PC back to the way it was
before any of this. Don't use terms like "physical address"
there is no "physical", only IP address. Correct
terminology will keep things clear.

For other
working pc, these two addresses are different. Does this mean
something?

I'm not going to try to interpret what you're describing any
more, only how it's supposed to be instead.

Do this - If your ISP has assigned you a fixed IP address
for your internet account (usually they don't, with most
ISPs, but you can ask them if your _Internet_ IP address is
"fixed" or "dynamic") then the router's WAN IP address
should be set to this. If your ISP doesn't assign a fixed
address, leave it set to "auto" or Dynamic.

Since some systems can connect to the internet through the
router (still?) this should still be ok.

Your router's LAN IP address should stay set to the default
(for the time being to get it working at least, and left
there unless you have a specific reason to change it later).
That address appears to be 192.168.0.1

None of your systems should have information entered into
their TCP/IP properties page for their network adapters. It
should be set to DHCP or Obtain IP address automatically and
Obtain DNS automatically.

/ under Block WAN Ping
When you "Block WAN Ping", you are causing the public WAN IP address on
the DI-624+ to not respond to ping commands. Pinging public WAN IP
addresses is a common method used by hackers to test whether your WAN
IP address is valid.

Discard PING from WAN side: Disabled

I meant discard PING from LAN side, it appears (since you
haen't mentioned such a setting) that your router doesn't
support this feature, so it will not be disabled, which is
OK.

/in run-cmd mode:
New pc can only ping itself. Can't ping router or other working pcs.
Working pc No.1 can ping working pc No.2.
Working pc No.1 can't ping New Pc.

You didn't tell us what IPCONFIG /all showed for the new PC.
Compare what it shows with what IPCONFIG /all shows for a
different PC that can connect to the router with ping and to
the internet. Do that after having set everything to auto
as mentioned above.

 

[zl79111]

In Dlink router, it is found there is a built-in firewall rule:
deny source(*.*) destination(LAN.* ) Protcal/port(*.*)
This might restrict the trafic pass through the DI-624+ router. This
rule can't be changed.

It was tried with the following added:
allow source(*.*) destination(LAN.* ) Protcal/port(*.*)
The above added rule was positioned with higher priority.

After re-do everything suggested and rebooting, I can ping router at
192.168.0.1 and can access www.Yahoo.com. But this only lasted for 5
minutes.

After losing internet, using ipconfig /all got funny ip address,
neither router (192.16.....) nor ISP (213.10.......).

Rebooting the pc can't get correct IP back. Again, other pcs are
working ok.
Now DHCP does not assign correct IP.

Back to the topic of Mac address yesterday
I can see the from router->status -> device
LAN: Mac address (00-11-xx-xx-xx-xx)
IP address (192.168.0.1)

WAN: Mac address (00-16-xx-xx-xx-xx) ----------- Note
IP address (213.10x.x.xxx)

From ipconfig /all:

NEW pc: Ethernet adapt Local Area Connection
Description: Intel(R) 82562v **************
physical address: (00-16-xx-xx-xx-xx) ------exactly
same as WAN mac address

When plugging the same ethernet cable to the other pc
Other pc: Ethernet adapt Local Area Connection
Description: Intel(R) PRO/1000 **************
physical address: (00-08-xx-xx-xx-xx)

Hope the information is useful.

 

[kony]

In Dlink router, it is found there is a built-in firewall rule:
deny source(*.*) destination(LAN.* ) Protcal/port(*.*)
This might restrict the trafic pass through the DI-624+ router. This
rule can't be changed.

It can't be as you state, because a wildcard would prevent
all traffic, it couldn't route anything without the firewall
stopping it ALL. I suggest this is only an example to help
the user make rules where actual values are input in place
of the asterik.

It was tried with the following added:
allow source(*.*) destination(LAN.* ) Protcal/port(*.*)
The above added rule was positioned with higher priority.

After re-do everything suggested and rebooting, I can ping router at
192.168.0.1 and can access www.Yahoo.com. But this only lasted for 5
minutes.

After losing internet, using ipconfig /all got funny ip address,
neither router (192.16.....) nor ISP (213.10.......).

You are trying to give only some short overview or summary
type of description which is exactly why you still have
problems. Instead, we needed a complete description, a
complete feedback about what you tried as you tried it, and
what the result was.

It is not just a matter of trying things, it is a matter of
exactly what, exactly when, and exact description. A step
by step coverage of the procedures as suggested.

We don't even know if you ever reset EVERYTHING to the way
it way before this new PC came into the equation, including
whatever you did with the ISP.

One last try - Reset everything to the way it was at first.
Undo everything you did to the Dell PC. Plug the Dell PC
into the router port. Note that the router and PC
connection lights are lit.

Power cycle the router, then the Dell PC. Run the windows
connection wizard. Ping the router. Next ping the router
from another system. If ping works, try tracert yahoo.com,
see if it finds a DNS server and then finds yahoo.com at the
command prompt. Try IE. Try OE or Firefox. I am tired of
making suggestions because you did not report back item by
item and it wasted a lot of our time. Based on every little
thing you might've reported back, it would have suggested
what to do next, but you did not do so, and now we can't
isolate the problem.

I am done troubleshooting this issue because you didn't
systematically follow through. Since this is a new Dell you
might contact Dell support, they should be able to at least
ensure the PC is configured correctly and if they installed
some kind of invasive software like that from McAfee or
Norton/Symantec, they can guide you in reconfiguration or
uninstallation.

 

[jaster]

In Dlink router, it is found there is a built-in firewall rule:
deny source(*.*) destination(LAN.* ) Protcal/port(*.*)
This might restrict the trafic pass through the DI-624+ router. This rule
can't be changed.

It was tried with the following added:
allow source(*.*) destination(LAN.* ) Protcal/port(*.*)
The above added rule was positioned with higher priority.

I don't know this firewall but it looks like basic firewall. Use
higher priority allow but the lowest priority is to deny traffic. Unless
match to specific allow rule fall thru to deny rule. I think this
firewall was disabled because other pcs got thru.

After re-do everything suggested and rebooting, I can ping router at
192.168.0.1 and can access www.Yahoo.com. But this only lasted for 5
minutes.

So why did it last only 5 minutes? Shouldn't happen.

This is starting to sound like a bad ethernet card or virus. You could
try "eventvwr.mmc /s" from the start -> run to review your
events around the time of losing the interrnet.

But a bad ethernet card is time to call Dell because maybe your card is
having IRC conflicts? Control Panel -> system -> hardware setting

You should set everything back to the point where you were
connected for the 5 minutes. Then figure out why you lost your
connection. I think that's the key to your story.

IIRC, you said the cat-5 connections on the router work because the other
pc connected without problem so the issue is with the Dell. (And you're
using a port 1-4? )

After losing internet, using ipconfig /all got funny ip address, neither
router (192.16.....) nor ISP (213.10.......).

213.10.x.x for your DNS addresses is correct.


The problem with DHCP is the DHCP assigns dynamic addresses unless
programmed to do otherwise. Some like yourself assign static IP addresses
in the PC. In my router I assign static IP addresses by the MAC
addresses of attached devices then if I switch or upgrade the OS that
ethernet MAC address is assigned the same static IP address.

Rebooting the pc can't get correct IP back. Again, other pcs are working
ok.
Now DHCP does not assign correct IP.

Your new PC should have been assigned an IP address if you changed nothing
and not necessarily 192.x.x.102.

Back to the topic of Mac address yesterday I can see the from
router->status -> device LAN: Mac address (00-11-xx-xx-xx-xx)
IP address (192.168.0.1)

WAN: Mac address (00-16-xx-xx-xx-xx) ----------- Note
IP address (213.10x.x.xxx)

These are as expected.

NEW pc: Ethernet adapt Local Area Connection
Description: Intel(R) 82562v ************** physical
address: (00-16-xx-xx-xx-xx) ------exactly
same as WAN mac address

When plugging the same ethernet cable to the other pc Other pc: Ethernet
adapt Local Area Connection
Description: Intel(R) PRO/1000 ************** physical
address: (00-08-xx-xx-xx-xx)

Hope the information is useful.

Sorry not at all. Not sure how you're looking at what on what.
So I ask
#1 that you do not change firewall settings on router because the
other PCs are working.

#2 connect the Dell to the router and use one of the working PCs to check
the router to see if the Dell shows up.

#3 cut and past output from ipconfig /all on the Dell after connection
to router.

#4 On Dell run tracert www.yahoo.com ( or 192.168.0.1
which should be just one line of output)

# run netstat -er
You should see something like

Interface Statistics

Received Sent

Bytes 14439368 14439050

Unicast packets 124285 124413

Non-unicast packets 68 72

Discards 0 0

Errors 0 129

Unknown protocols 0

Route Table
Active Routes:
Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20

192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20

224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20

255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1

Default Gateway: 192.168.0.1

# you can run netstat /? for a help but

netstat -bv for a list of programs accessing you connections

netstat -s for statistics on the connections. Of significance are the
errors, discarded and failed attempts.

 

[zl79111]

Many thanks for all of you offering advice and support.

All these funny things encountered can be solved by using a D-link
wireless usb adaptor. After the installation, the wireless access
works. Disable the wireless and plug the ethernet cable, the wired
access also start working. I am not a computer expert and there must
be someone out there knows why.

Best wishes to you all.