Networking will not see non-windows 7 computers.

iguana said:

Well interesting enough we just found out how to solve the problem, and it worked on every machine that was having a problem, INCLUDING an xp machine which wasn't seeing the other machines on the network.

We just went and network mapped all the machines on the network manually, on the final map of the last machine, we put in the login/pass for that machine, and then suddenly every appeared in the network explorer window.

We duplicated the proceedure on each affected machine and on the last manual map, everything became visible in that machine's network explorer.


I'm guessing that a master browser list somewhere was not initializing or something until that last login/password of the manual mapping was done?

huge relief, but what a messed up reason. I appreciate everyone who weighed in trying to help solve the problem.


Steve.

i was reading this thread like it was a thriller, sometimes i thought it's me, who is writing your posts
i am very happy to hear, that you solved the problem, but please, can you describe me the process of "network mapping all the machines on the network manually" as this is what i am trying to do tomorrow, but i have no idea, what do you mean by that

Can't blame you guys for getting frustrated with this. I would be so unhappy resorting to network mapping when the GUI works perfectly fine. Might as well go back to using Windows 98 if you need to resort to network mapping.

But the problem wasn't solved with network mapping it was worked around but not solved!

I mean the whole point to Windows 7 is the cool looking and intuative GUI for networking. Whats the point of using Windows 7 if you aren't using it?

I'd rather die of old age trying to make it work than to resort to Windows 98 style network mapping.

I think there was only one build where I had to work a little harder to get the XP machine to show up but even then it only took ten minutes.

Hey,

hope this helps

Link Layer Topology Discovery For XP (LLTD) Responder (KB922120 - Bing

Hey there,.. sorry for the late follow up replies.

Everything seems to be running fine since the last post. So somewhere the master browser record was just not updating until we did the manual mapping.

drvic10k: I see you have private msg'd me as well.. but what I meant by the manual mapping is typing in the UNC path to the shared folder/drive on the computer you want to network with.

it would look like this... \\COMPUTERNAME\drivename

Once you do that successfully you get a browser window inside your explorer window for that drive/share. You can then drag a link to you desktop and it will interface with that drive/share via the network each time you click on it. (there are other ways to accomplish the same result using different approaches, but the result is the same).

You can also use the direct IP, usually something like 192.168.x.x (I believe from an explorer window you can type it directly, or you have to type rfp:\\192.168.x.x)

Anyway.. will follow up with your private msg's as well.

Steve.

Sorry for digging from the grave, but I have exact problem with the thread owner. I did try his manually mapping method but that doesn't seem to help in my case.

I have 3 windows machine and several linux NAS boxes, windows XP, Solaris that used to be shown all in the networking, they all use WORKGROUP name. After restarting my COMCAST router, only windows 7 machines are shown in networking, the other linux boxes, i have to manually type in to access the files, all 3 windows 7 machines stop seeing them in networking.

I tried rename the workgroup to HOME, the windows 7 machine can see all the machines again (within the workgroup HOME). But the thing is some my NAS boxes I can't change workgroup name to HOME, because WORKGROUP is the default from manufacture.

Is there anyway that I can make my WORKGROUP working again?

thanks

anyone?