Solved An error happened during the mapping process.

[chev65]

Honestly this problem with the map hardly ever comes up or I might have had some better answers for you. I'm pretty sure there is a program causing this to happen but the only way to nail it down is to install your programs one at a time and check the map after installing each. Might be interesting to see which one is causing the problem.

 

[soho1]

Other than that I would install any of the Windows updates that apply to your system.

It's a new PC with all udpates applied. Sometime, before applying all updates, this network mapping worked.

 

[soho1]

Honestly this problem with the map hardly ever comes up or I might have had some better answers for you. I'm pretty sure there is a program causing this to happen but the only way to nail it down is to install your programs one at a time and check the map after installing each. Might be interesting to see which one is causing the problem.

I'll let you know, after the system restore completes and I start again.

 

[chev65]

I had a problem like this just the other day. One of my programs "a driver in this case" was causing my movies to not have sound when I hit the play button on WMP. I couldn't figure out which program it was so I uninstalled the Op system and installed one program at a time, testing WMP after each install.

After installing my programs one at a time and checking WMP each time, I found out that somehow the driver for my Logitech G15 keyboard was indeed responsible for the problem. It was like hitting a switch, install keyboard driver, lose sound when I hit the play button, uninstall keyboard drivers and the sound works again just like clock work. I also tried to disable certain files in the driver set but nothing seemed to work.

I just had to have the drivers installed for my G15 keyboard because the LED feature with the systems read out from Everest is really cool.

I ended up finding a work around which was to hit the start button on WMP, then after the movie sound didn't start, go back and use the "play" option in the menu to play the movie with sound, it took me awhile just to figure that out but it works everytime. All the other windows sounds worked and it appeared to have nothing to do with my Xonar D2 sound drivers.

Logitech, in their infinate wisdom, apparently did not test this out before they released the new driver. I googled the problem but didn't find anything on it which was hard to believe.

 

[soho1]

WELL!

After extensive poking about, I find that the Network Map function works just fine, as long as my Epson Workforce 600 is NOT plugged into the router. Now, I don't know WHY I could see see the printer on the map when I first got this PC, but I cannot map it now. Admittedly, the thing that is different is the Firmware update to the router BIOS. There is no going back however. Very disappointing though.

@Chev65 I want to thank you for the help and if you have any further suggestions let me know, but I may have to "let go" of this. I will make a note to self that when I need a network map, unplug the Epson from the D-Link so that Windows 7 can work.

@B.F.Skinner Have you considered the ramifications of technology in your studies?

 

[soho1]

Epilogue: It's the D-Link firmware

... I will make a note to self that when I need a network map, unplug the Epson from the D-Link so that Windows 7 can work.

Epilogue

I ended up configuring the Epson Workforce 600 for wireless. This gave me the ability to simply turn off the Epson printer so the D-Link router doesn't see it (which it does when plugged in with Ethernet cable). Then, Windows 7 can create the network map in the Network and Sharing Center without any problem.

My conclusion, from the entire episode is not that it's the Epson, which used to display on my network map prior to the firmware update, but that the problem stems from the D-Link router firmware upgrade. The old BIOS, version 1.10 seems to have been LLTD (Link Layer Topology Discovery) compatible, but the new firmware appears not completely compatible, giving Windows 7 a problem and reporting the error "An error happened during the mapping process".

I hope this helps someone else in the future.

 

[chev65]

WELL!

After extensive poking about, I find that the Network Map function works just fine, as long as my Epson Workforce 600 is NOT plugged into the router. Now, I don't know WHY I could see see the printer on the map when I first got this PC, but I cannot map it now. Admittedly, the thing that is different is the Firmware update to the router BIOS. There is no going back however. Very disappointing though.

@Chev65 I want to thank you for the help and if you have any further suggestions let me know, but I may have to "let go" of this. I will make a note to self that when I need a network map, unplug the Epson from the D-Link so that Windows 7 can work.

@B.F.Skinner Have you considered the ramifications of technology in your studies?

I can't say I'm not surprized. It's kind of the same thing as me where a problem is created by another software but in this case it's a piece of hardware just being plugged into the router causing the problem. It's not easy to nail these problems down sometimes. The network map is no big deal and if you need it you can always unplug the printer I guess. Maybe if you mess with the router settings you can get it to work with the map.

 

[studioCJF]

My conclusion, from the entire episode is not that it's the Epson, which used to display on my network map prior to the firmware update, but that the problem stems from the D-Link router firmware upgrade. The old BIOS, version 1.10 seems to have been LLTD (Link Layer Topology Discovery) compatible, but the new firmware appears not completely compatible, giving Windows 7 a problem and reporting the error "An error happened during the mapping process".

I know this is an old post but I have been having this problem for a while on my desktop with Windows 7-pro (64bit) but thought that it was a problem with my laptop being on XP-SP3... I cleaned/reformatted the laptop and installed Windows 7-Pro (32bit) and the problem still exists. I don't think it has anything to do with the 64bit -v- 32bit but I do have basically the same router (D-Link DGL-4500) and the desktop PC mapped fine with the older firmware. I added a DAP-1522 as a wireless bridge for my AV equipment and had to update the firmware on the DGL-4500 in order for the two devices to talk to each other. So I agree that it must be a D-Link firmware issue at this point.

One last thing... I found that if you uncheck the LLTD Responder in the network adapter settings on the PC that you are using to generate the map then you will get a map but the other PC will be listed at the bottom but not placed in the map. if you reselect the LLTD Responder and go to your other PC and unselect the LLTD Responder the you will get a map with the other PC shown at the bottom and not on the map.

No sure if this helps anyone but at least it is a partial work-around and maybe it helps isolate the problem belonging to the LLTD Responder and not the LLTD Mapper

YMMV

 

[Chinch]

interesting discussion, guys... i came across it while investigating this same problem.

i can say, it could be no coincidence that i also have a D-Link DIR-655 router with up to date firmware. the tip about disabling the LLTD responder in the adapter was a good one, i wouldn't have thought to do that, personally. i tried it though, and what happens? the network map comes up -- albeit a bit... strange. basically i have two peer computers going into the router (right now), then the router to the internet. i only notice one oddity. not sure if this thing will let me upload my screenshot or not, but *my* computer goes through an "Unknown" intermediary device, then the router. i am assuming this is the D-Link screwing stuff up, since as it says right from the help file:

The device doesn't support the required protocols for Windows 7, which can cause some devices to appear on the network map, but not as you'd expect to see them. For example, a router could be shown as three things: a router, a switch, and an access point.

i don't know if that actually means simultaneously or as one of the three. if the former were true, then that could easily explain this "Unknown" device between me and my router. Just FYI, the computer is wired directly into the router port.

just thought i would throw my experience in here in case someone stumbles upon this later on down the road like i did...

and btw, it did let me attach my screenshot. names of the computers and my ssid have been removed to protect the innocent. the top computer on the left is mine, the bottom on the left is my brother's (also win7 x64 ultimate). i notice that all connections through the map are two solid green lines, except his connection line is sort of "dashed". i'm not quite sure what that means.

i didn't even need a network map really, it just bothered me that it didn't work, haha...

 

[mediaman09]

My conclusion, from the entire episode..... the problem stems from the D-Link router firmware upgrade. The old BIOS, version 1.10 seems to have been LLTD (Link Layer Topology Discovery......I hope this helps someone else in the future.

soho1,

It has helped!

I followed this post with great interest as I have the identical problem re network maps , as well as the DIR 655 router (hardware rev A3).

I rarely use the network map, so its not critical, but I too like things to work... but only to a point. I draw the troubleshooting line, on these type of issuss, when the suggested sources start to include bad sectors, reinstalling Win 7, AV, firewalls, removing devices etc. Sometimes indeed they are the issues, and I would (and have) gone that route for mission critical issues , but not for this one.

But it great you determined the source re the firmware upgrade.

I have firmware ver 1.35NA, 2010/11/12 . Just chekced and its the latest, so hope is not good for a upgrade anytime soon.

You mentioned earlier in the post about a trial third party mapping tool .. Was it any good? Can you provide a link? Ever find a free one?

 

[soho1]

It's something in the DIR-655 firmware.