This is why routers suck!

[Hígh Treason]

This isn't the fault of KC, it's the fault of my router.

It's amazing what you can find out with a clean install, for a long time I have had problems with my network, I ask for something off a machine and have to wait half an hour for the log-in box to appear or for a timout message. With a clean install of Windows on one of my spare systems (A crappy AMD Athlon XP 2600+ Sample) I tried to get some drivers and stuff that were stored on another system (Alyssa) - all my network settings are correct. It didn't work, so I starte playing around, this is basically what I found;

Code:

C:\Documents and Settings\High Treason>tracert alyssa

Tracing route to alyssa.dlink.com [67.63.55.11]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    34 ms    34 ms    33 ms  adsl-83-100-230-254.karoo.KCOM.COM [83.100.230.254]
  3    34 ms    34 ms    34 ms  10.102.243.241
  4    34 ms    34 ms    34 ms  10.102.240.221
  5    37 ms    37 ms    37 ms  10.55.0.225
  6    37 ms    37 ms    37 ms  212.187.137.133
  7    37 ms    36 ms    36 ms  ae-11-11.car1.Manchesteruk1.Level3.net [4.69.133.97]
  8    43 ms    43 ms    43 ms  ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
  9    43 ms    43 ms    44 ms  ae-58-113.csw1.London1.Level3.net [4.69.153.122]

 10    43 ms    43 ms    42 ms  ae-12-51.car2.London1.Level3.net [4.69.139.67]
 11    43 ms    43 ms    43 ms  savvis [4.68.127.34]
 12    62 ms    44 ms    44 ms  204.70.206.65
 13   118 ms   118 ms   120 ms  cr2-pos-0-0-3-3.Washington.savvis.net [204.70.196.126]
 14   118 ms   117 ms   218 ms  acr2-so-4-0-0.washington.savvis.net [204.70.196.182]
 15   118 ms   118 ms   118 ms  208.173.10.98
 16   117 ms   118 ms   117 ms  67.63.55.11

Trace complete.

C:\Documents and Settings\High Treason>

Looks like my router's DNS is lying to the computers on my local network, I get the same kind of results from everything on my LAN... I never thought to trace the route on my LAN before, this is garbage!

[Adrian]

What you using as your DNS server? Doesn't your router pull in KC's DNS?

[Hígh Treason]

My router acts as the DNS Server for the LAN, the router does indeed rely on the KC DNS Servers for anything outside of my LAN.

Never had any trouble like this when I had a server to take care of such things.

[Adrian]

Do you get this if you use a different DNS server?

[commandergc]

is your computer actually connecting to your routers DNS? cos i get what you're seeing when i have open DNS updater running on my pc. disable it and reset dns to my router and i get just one hop.

[Hígh Treason]

If I use a different DNS Server I get similar results, when I actually had a server, I never really had any trouble with this.

My router is definitely acting as the DNS as all my connections are manually configured. Oddly, it's half-way working again, Machine A can talk to Machine B but not the other way around, and I don't doubt it will break again at somepoint. I've pretty much abandoned having a network at all by this point anyway, so much for those thousands I spent updating the whole thing.

[TJ]

Why when you do a tracert to alyssa does your pc tell the router to tracert to alyssa.dlink.com

This appears to be a PC problem not a router one.

[Soul Cruiser]

Am I missing something here?

Are you trying to TR another machine on your LAN or something at dlink.com?
Dlink IP trace replies in 23 hops, as does a DNS trace.

I TR on my LAN without an issue and I don't use Karoo DNS Servers but I do not have a domain set up now.
I TR to dsldevice.lan no probs.

Perhaps a little more detail?

[Hígh Treason]

Alyssa is a workstation on the LAN, it should resolve as "alyssa" or "alyssa.treason.dyndns.org" but the router stores this incorrectly as alyssa.dlink.com, this is obviously an invalid name.

It doesn't really matter, I have one machine connected to the router now and I threw over $2000 worth of network hardware in the garbage after introducing it to my boot, it felt quite good curb stomping it after all the crap it put me through to be honest.

[David]

Tried looking here?

[Hígh Treason]

I did, as I stated earlier, everything was manually configured, this is a problem with the router and not the computer.

[Soul Cruiser]

I can see now why you enjoyed the stomping lol

I have seen this behavior on a domain before usually resolved with a manual entry in the hosts file.
But I'm no router guru. I would have thought it would of at least allowed you to resolve your client names to IP addresses via the internal DNS server thus allowing ease of access within your LAN but then I've never used a DLink either.

Well at least enjoyed one small part of it.