D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: WimpMiester on April 11, 2012, 03:36:58 PM
-
Found this old topic with no response and I am having the same problem using the DGL-4500 firmware 1.23na, Hardware A1.
Had a functional home network and my router died.
Bought a D-Link N130 (DIR-601), setup went quick and fast, all computers can access the Internet.
Computer name IP
Basement (XP, SP3) 192.168.0.101
Office (W7) 192.168.0.102
Blaptop (XP, SP3) 192.168.0.103
Dlaptop (XP, SP3) 192.168.0.104
Brothersprint 192.168.0.105 printer hanging on the network
All computers are in the same workgroup
Tried to connect to Basement from Blaptop, would not connect. “Windows cannot find \\Basement.
I ping’ed 192.168.0.101 answered ping, no packet loss
I ping’ed Basement replied with Basement.wor.rr.com [208.67.216.145], no packet loss (Had this like , what the ….., reaction)
I ping’ed 192.168.1.102 answered ping, no packet loss
I ping’ed Office replied with Office.wor.rr.com [208.67.216.145] , no packet loss (Yep, same IP)
Searched the forumns and turned off Advanced DNS Service
Now when I ping Basement, it replies with "could not find host Basement"
I hand jammed the names/IPs into all the computer hosts files. Cleared arp, cleared the IP stack.
Pinged 192.168.1.101 no response
Pinged Basement replied with Basement [192.168.1.101], but no response.
Any ideas?
Started with windows 7 and homegroup. Think its IPv6 related. Can get to any lan device fine by IP but buy name all resolve to this external IP 208.67.216.145.
-
Under BASIC -> Network settings:
What settings are you using? Can you take a screen-shot? I just need to see the first two sections.
I don't think this is related to IPv6. This is more related to NetBIOS/WINS (If I'm thinking correctly).
-
Here is a picture of my settings. I can access the other laptop just fine by using the host name.
(https://cloud.dsop.co/apps/files_sharing/get.php?token=d09fb11d5dec9e357662fed4880b86c09bf225f9)
This is a snippit of the help file so you can understand what settings do what:
Device Name
Device Name allows you to configure this deice easily when your network using TCP/IP protocol. You can enter the device name of the router, instead of IP address, into your web browser to access for configuration. Recommend to change the device name if there is more than one D-Link devices within the subnet.
Local Domain Name
This entry is optional. Enter a domain name for the local network. The AP's DHCP server will give this domain name to the computers on the wireless LAN. So, for example, if you enter mynetwork.net here, and you have a wireless laptop with a name of chris, that laptop will be known as chris.mynetwork.net. Note, however, if the AP's settings specify "DHCP (Dynamic)" Address, and the rou ter's DHCP server assigns a domain name to the AP, that domain name will override any name you enter here.
Always Broadcast
If all the computers on the LAN successfully obtain their IP addresses from the router's DHCP server as expected, this option can remain disabled. However, if one of the computers on the LAN fails to obtain an IP address from the router's DHCP server, it may have an old DHCP client that incorrectly turns off the broadcast flag of DHCP packets. Enabling this option will cause the router to always broadcast its responses to all clients, thereby working around the problem, at the cost of increased broadcast traffic on the LAN.
NetBIOS Announcement
Check this box to allow the DHCP Server to offer NetBIOS configuration settings to the LAN hosts. NetBIOS allow LAN hosts to discover all other computers within the network, e.g. within Network Neighbourhood.
Learn NetBIOS information from WAN
If NetBIOS advertisement is swicthed on, switching this setting on causes WINS information to be learned from the WAN side, if available. Turn this setting off to configure manually.
NetBIOS Registration mode
Indicates how network hosts are to perform NetBIOS name registration and discovery.
H-Node, this indicates a Hybrid-State of operation. First WINS servers are tried, if any, followed by local network broadcast. This is generally the preferred mode if you have configured WINS servers.
M-Node (default), this indicates a Mixed-Mode of operation. First Broadcast operation is performed to register hosts and discover other hosts, if broadcast operation fails, WINS servers are tried, if any. This mode favours broadcast operation which may be preferred if WINS servers are reachable by a slow network link and the majority of network services such as servers and printers are local to the LAN.
P-Node, this indicates to use WINS servers ONLY. This setting is useful to force all NetBIOS operation to the configured WINS servers. You must have configured at least the primary WINS server IP to point to a working WINS server.
B-Node, this indicates to use local network broadcast ONLY. This setting is useful where there are no WINS servers available, however, it is preferred you try M-Node operation first.
This setting has no effect if the 'Learn NetBIOS information from WAN' is activated.
Hope this helps..
-
Some things to try:
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking
Ensure devices are set to auto obtain an IP address.
Always broadcast : Enable (compatibility for some DHCP Clients)
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking.
Remember this router doesn't support IPv6 so if your using Vista or Windows 7, you can disable IPv6 under the network properties while using this router.
-
D 'Oh!! You are putting in the correct hostname, right? Windows 7 adds -PC to the end of the hostname.. :D
Go under Network. You should see all of the computers in the same workgroup with their name.
Hope this helps. :) Enable Advanced DNS Service has to be UN-checked for this to work.
-
OK, I already have everything the way you say except I didn't have a local domain name and I turned off Advanced DNS. The only thing that changed is now if I "tracert" an invalid name it can't resolve it. Everything went to that IP address before. Also, If I trace it-self it comes back correctly. But still if I trace anything on the local net it goes somewhere outside the network to try and resolve it. So instead of going to 208.67.216.145, now with Advanced DNS off it goes to 66.152.109.25. I tried all the DHCP mode options and check boxes and DNS relay off all with the same results.
-
who do those 2 IP addresses belong too? Try using domaintools.com and see.
Seems like something on your network is redirecting traffic.
Can you install a external Gb network switch and test again?
-
The IP changes by whats in the "Host name" under internet settings. This was always blank, but if I put something in there the IP it traces to changes.
-
It's working normal. If you have Advanced DNS Service enabled, it will not work (You said it's disabled).
It should work if you are putting in the full hostname, like ping basement-PC (From the post you quoted from).
What happens when you select: Start -> Network? What computers do you see?
Also, if you have a Device Name listed for the 4500, can you simply type in that name and it forwards to the login page of the 4500?
-
Everything shows correctly under Windows Network. And I can browse, share files with no problems. But if I try to use remote desktop by name or trace any computer/device by name it goes to and external IP. So if I say "ping -a 192.168.0.10" for example. I'll get back the correct IP, like mycomputer-pc [192.168.0.10]. But then if I "tracert mycomputer-pc" I get "Tracing route to mycomputer-pc.charter.com [208.67.216.145] over a maximum of 30 hops:....". And 208.67.216.145 is what it looks for with Advanced DNS on and 66.152.109.25 with Advanced DNS off.
Seems to me that when doing a DNS lookup by name the router is looking externaly first instead of internaly first. If I could revert back to firmware 1.15 which never gave me any problems, I could eliminate the 1.2x firmware as the issue.
-
If I could revert back to firmware 1.15 which never gave me any problems, I could eliminate the 1.2x firmware as the issue.
When you upgraded your firmware, did you save the configuration and then load the configuration on the new firmware?
If so, I think you need to Restore to factory defaults, and manually enter in everything. There is some code/configuration that is not working.
If you have the settings identical to mine, and Advanced DNS Service un-checked, it shouldn't forward to charter.com.
Reason I think it's that, is I'm running 1.23NA and it's working on my end. I don't think it's the firmware version. I think this might fix your other issues as well.
-
Yes, I loaded the saved config each time the firmware was upgrade, as suggested by the documentation at the time. I will try redoing everything from scratch but not today, probably on the weekend.
-
Even though its' recommended saving configuration files for each FW build that you use. We've found out that going from one major FW version to another with different configuration files causes some issues to be seen. So when you went from v1.15 to 1.2x, this is a major verion change thus the saved configuration file captured while using v1.15 will not work well on v1.2x. Once your on 1.2x, you need to set up from scratch and then do another save. I name all my config files to the following: Date/mode/Rev/FWversion, i.e. 20120410DGL4500RevA1v123
Once your on 1.2x you can't downgrade to v1.15.
-
Decided to just do it. I reset factory defaults from the GUI and then with the button on the back. Re-entered everything. That same thing still happens. Didn't fix it.
-
Maybe someone can view your settings via TeamViewer.
Furry, can you ping another computer on your LAN via name? I don't think I am the only one. I thought the settings I brought up was tied into this. Do you have NetBIOS Announcement checked? That has to be checked so the 4500 will pass the information.
-
I checked that and tried to ping from my Mac Book my Server. Could not get the host name to make contact. Only the IP address. I'll try after work to ping from my XP box.
-
Here is something interesting to add. I connected and old networked harddrive who's SMB server worked with XP (Can access as network shared drive) but not Vista/7. It will correctly resolve a trace by name to it! So, looks like the router has an issue with Vista/7 and the way they handle name resolution, but older stuff is ok.
-
Wonder if there is an issue with Vista/7. I know there are some major differences in Vista and 7 vs XP regarding networking. :-\ I try my 7 and XP when I get home and see.
-
Both of my laptops are running Windows 7.
-
Maybe you can review his set up with him sometime on teamviewer Frag. ;)
-
I don't have an issue with that. PM me the time-frame/day you are available to do this. I am somewhat free tomorrow/Sunday during the day.
-
I checked that and tried to ping from my Mac Book my Server. Could not get the host name to make contact. Only the IP address. I'll try after work to ping from my XP box.
See, there is something wrong, you found the same issue I'm having.
-
Well, the only things that can be different are the 4500 settings, and the OS'es...
-
Possible however not fully confirmed as I was using OSX and not XP or Windows. I'll test this weekend. Lets see if Frag can review your settings and see whats going on with yours.
See, there is something wrong, you found the same issue I'm having.
-
The router definitely has a problem with Vista/7 PC's. I can successfully trace an XP computer and old non-vista/7 compatible nas box. But can't trace a Vista/7 PC. When tracing works you get just the name returned.
For example; Do a "tracert mycomputer", you get "1 <1 ms <1 ms <1 ms mycomputer [192.168.0.8]", which is what it should return. But when tracing a Vista/7 PC, “tracert mycomputer-pc” you get "1 <1 ms <1 ms <1 ms mycomputer-pc.charter.com [66.152.109.25]". Notice it returns the full domain and resolves everything to the same external IP.
There is nothing a user can configure in the router to fix this. This clearly is a firmware bug.
-
Its not a bug. Its how DNS works with Vista and on. Perhaps this will shed some light on it.
http://www.simpledns.com/kb.aspx?kbid=1232 (http://www.simpledns.com/kb.aspx?kbid=1232)
-
If this is a 'bug', then why am I able to ping my Synology NAS, and my other Windows 7 computer (From a Windows 7 computer)?? Unfortunately, I don't have Vista on anything, so I can't check it, but clearly it does work.
Microsoft Windows [Version 6.1.7601] My Windows 7 computer
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Alienware>ping fileserver Synology NAS
Pinging fileserver [192.168.0.105] with 32 bytes of data:
Reply from 192.168.0.105: bytes=32 time<1ms TTL=64
Reply from 192.168.0.105: bytes=32 time=1ms TTL=64
Reply from 192.168.0.105: bytes=32 time=1ms TTL=64
Reply from 192.168.0.105: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.0.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\Alienware>ping fluffybuds-PC Fiance's Windows 7 computer
Pinging Fluffybuds-PC [192.168.0.108] with 32 bytes of data:
Reply from 192.168.0.108: bytes=32 time=1ms TTL=128
Reply from 192.168.0.108: bytes=32 time=1ms TTL=128
Reply from 192.168.0.108: bytes=32 time=2ms TTL=128
Reply from 192.168.0.108: bytes=32 time=2ms TTL=128
Ping statistics for 192.168.0.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Alienware>ping DLink D-Link 4500
Pinging DLink [192.168.0.1] with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\Alienware>
-
Because your doing a ping. Pinging works, it's a name trace that doesn't.
-
Heres my XP Pro tracert:
C:\Documents and Settings\>tracert sae
Tracing route to sae [192.168.0.107]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.107
Trace complete.
C:\Documents and Settings\tracert server
Tracing route to server [192.168.0.100]
over a maximum of 30 hops:
1 4294967294 ms <1 ms <1 ms 192.168.0.100
Trace complete.
Heres my Windows 7:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\>tracert sae
Tracing route to sae [192.168.0.107]
over a maximum of 30 hops:
1 4 ms 1 ms 1 ms SAE [192.168.0.107]
Trace complete.
C:\Users\>tracert server
Tracing route to Server [fe80::91d:5153:61a4:47ea%10]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms Server [fe80::91d:5153:61a4:47ea]
Trace complete.
-
Because your doing a ping. Pinging works, it's a name trace that doesn't.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Alienware>tracert fileserver
Tracing route to fileserver [192.168.0.105]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms FILESERVER [192.168.0.105]
Trace complete.
C:\Users\Alienware>tracert fluffybuds-PC
Tracing route to Fluffybuds-PC [192.168.0.108]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Fluffybuds-PC [192.168.0.108]
Trace complete.
C:\Users\Alienware>tracert DLink
Tracing route to DLink [192.168.0.1]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.0.1
Trace complete.
C:\Users\Alienware>
-
Any status on this?
-
What I've found is that with Advanced DNS Services enabled name resolution doesn't work. With Advanced DNS Services disabled and leaving host name, local domain name blank (defaults), computers and devices prior to Vista, name trace works. If I enter anything in host name and/or local domain name it no longer works at all. Even if the host name is the same as what's configured automatically.
I tried reverting the router to factory defaults, using only factory settings, let PC's get new IP's and still doesn't work. I've change which PC is the master browser and nothing changed. So, I see no solution for this problem.
-
I've got a Vista image at home I can give it a go. I'll load it up and test it out and see.