Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nrf]

I tried this and it made the map-builder in vista report an error, which goes away when I disable this feature.

another half-done feature...

[ECF]

What does the error state? I haven't seen an error when using this feature.

[nrf]

"An error happened during the mapping process. Click here for more information"

clicking on 'here' gives you an entry in the help file which is very general / useless:

A message is displayed, saying that an error occurred during the mapping process.
This can occur for the following reasons:

A computer or device on the network restarted during the mapping process. To fix this problem, wait for the computer or device to finish starting up, and then refresh the network map by clicking the Refresh button . <did not happen, refresh as many times as you like>

Your computer is connected to a wireless network and the wireless signal quality is poor or intermittent. To fix this problem, move your computer closer to the wireless router or access point. <n/a, wired network only>

A device on the network, such as a hub or switch, is not working properly or is not compatible with the Link Layer Topology Discovery (LLTD) protocol, which Windows uses to create the map. To fix this problem, disable the device, turn it off, or remove it from your network.<the closest candidate>

Responses from other devices on the network are delayed or there is an incompatible router on the network. If responses are delayed, try waiting a few minutes and then refreshing the network map by clicking the Refresh button . If a router is incompatible, try disabling the router, turning it off, or removing it from your network. <another way of saying the previous one>

[ECF]

What devices does you network consist of and what firmware version are you using?  I have not been able to replicate this error using it using firmware 1.01.

[nrf]

cablemodem->dgl4300 with recent firmware, locally connected to a smc ezstream and a dell pc, the 4300 is hardwired upstairs to a dgs2208 switch. on the switch are a laptop, vista pc, 3 xp pcs, a linux pc, a dvg5102s TA, and the dns123. (hmmm. heavily d-link!) dns is the 1.01 firmware.

I get the map just fine if the dns is told not to do lltd, but the error if it is.

[nrf]

I'd offer to get an ethernet trace but I don't have any hubs that would allow a tap.
as long as I am on the topic, I had been getting a nice picture of the dgl4300 until I upgraded its firmware last week, now it shows up as a generic switch and a separate 'access point'.

[ECF]

That is odd it may have something to do with the router not support LLTD because I do not see this issue and I haven't herd an complaints about it. I will have to setup a DGL-4300 and see if I get this error.

[nrf]

cool. good luck! by the way, I still had the error with the earlier 4300 firmware.
also, to put things in perspective, this issue is minor compared to application compatibility issues and low throughput with jumbo packets.

[ECF]

I tested it with a DGL-4300 with FW 1.06 and 1.09 and I did not get this error message.

[funchords]

If your network uses MAC filtering, then LLTD will be incompatible with your network. I do not know what the error message would be, as I do not have a DNS-321.

From microsoft -- http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/LLTD-spec.doc

The mapper uses generation numbers to generate fresh MAC addresses that are unknown to the switches in the network. This avoids the requirement of rebooting switches between mapping runs, so it is critical to choose an as-yet-unused generation number.

[nrf]

interesting to know this, I guess I'll scout around msoft some on this aspect (again). I only have MAC filtering for the wireless side which is turned off at present.

[funchords]

interesting to know this, I guess I'll scout around msoft some on this aspect (again). I only have MAC filtering for the wireless side which is turned off at present.

I hope you're using WPA or WPA2 on the wireless side.

Short Simple "Just Solve My Problem" Version:  If you use WPA or WPA2, then MAC filtering is redundant. (MAC Security isn't effective, anyway.)

Long Preachy Version:  MAC filtering is not security as MAC-layer is designed as an external visible address -- a way to provide low-layer connectivity (not security).  MAC addresses are always sent in the clear (even when encryption is used) and so MAC addresses are easily read and spoofed. Therefore, the only thing MAC filtering reliably does is make your network harder for you to administer.

(My rant,

In a race to outnumber one another in "features," the community of network vendors have done the residential consumer a disservice by doing things like MAC filtering or SSID "hiding" and calling them security. They are preying on your lack of knowledge that MAC addresses are attached to every frame in the clear. They're not security and weren't supposed to be. Your MAC address is meant to help you to be found and communicate correctly, not to help you block communications.

The reasons we have standards is to provide compatibility and interoperability so innovators can expect how things will behave and do neat new things like LLTD.  So when someone breaks those expectations, they risk impacting those innovations. 

MAC security? -- SSID "hiding"? -- Fehgeddaboudit.  These "features" are backwards.

Rant over.)

The reason you would use MAC addresses is to provide some kind of "I'm really a member of this club, I'm supposed to be here" assurance.  WEP, WPA and WPA2 all do this, (although WEP is too easily cracked and should not be used). 

[nrf]

the main point was that I don't filter the lan side so it could not be causing the error message.

you needn't worry about the security of my wireless system in this forum.

[nrf]

another data point - I'm trying out server 2008 enterprise from the same machine
and the error does NOT occur.

I don't totally trust the thing anyway as it is misreading which switch the 'gateway' is hooked to, but curiously I get the pretty picture of the DNS without installing anything.

nrf

[nrf]

in the process of playing with server 2008, I ended up switching NICs, and problem is resolved even for Vista Ultimate - evidently it has something against using the second NIC with the first one being disconnected.
nrf