Networking will not see non-windows 7 computers.

[Zardoc]

Do you have messages in the event viewer both on Win and XP relating to browser

Please see what I mean.

Common causes and solutions of browser Event ID 8021 and Event ID 8032 on domain master browsers

 

[dave1812]

have u tried this yet? http://www.microsoft.com/downloads/...1D-EE46-481E-BA11-37F485FA34EA&displaylang=en

 

[Zardoc]

I think that it's something very stupid either on the 7 box or the one it doesn't see.

It could have been that the Xp machine acted as a master browser which kept you from seeing it

You could also try to uninstall and reinstall network drivers on 7 machine that doesn't show xp machines.

You could also try to reset netesh dll library on 7 box, but usually that's when you don't see any network connections.

Click Start, and then click Run.
In the Run box, type cmd.exe, and then click OK.

Type the following lines. Press ENTER after you type each line. This command text is difficult to type. Be sure that you type it exactly as it appears below. Or you may find it easier to copy and paste the text instead. Click OK when the RegSvr32 dialog box appears for each command.

regsvr32 netshell.dll
regsvr32 netcfgx.dll
regsvr32 netman.dll

Restart the computer. Check to see whether your networking icons appear. If this method worked for you.

Post by Dave is another option.

 

[iguana]

Hi there,..

I did the .dll registering that you mentioned, it doesn't seem to have any effect.

I reinstalled the newest drivers for the network adapter.

I looked through the Event viewer and saw no instances of any browser errors. There are errors/warning/information entries, but I didnt see any that pertained exactly to networking.

and I didn't install the Link Layer Topology because the other win7 machine can see all the drives fine, so I felt that obviously those XP machines are broadcasting or that other win 7 machine would not be able to see them. Just this win 7 machine and another one on the network cannot see them.

still scratching my head.

Steve.

 

[chev65]

I've been sharing with my XP machine since Jan. and never had a single problem so unless something is blocking network access like a third part firewall there is nothing more you can do. The only thing I can think of is that file sharing isn't properly enabled on the XP machine. That was the only thing I ever had to do.

You shouldn't need to do any of the steps shown here today to gain simple file access from your Windows 7 machine to your XP machine. Both Public file sharing or Workgroups should be working for you without having to do anything other than the check list I already posted. Something other than Windows is preventing you from gaining access.

 

[iguana]

chev65,

I totally agree with you, and that is why this is so frustrating.

We have 3 windows 7 machines side by side... 2 other XP-pro machines sitting across the room, a couple of of xp servers in the back plus 5-6 macs, and a few misc vista/xp laptops.


The win 7 machines, 1 of the 3 can see the computers via the network explorer. All 3 win 7 machines can access the xp machines via typing in the \\COMPUTERNAME\drive directly. The xp machines and the win7 machines can ping each other via CMD.exe (ping 1921.168.1.xx)

If NONE of the win7 machines could see the xp machines I would go and install the LLT tools on the xp machines, and work with those as well. But one of the win7 machines (of the 3) can see everything just fine, and has the same sharing/workgroup/iv4/iv6/adapater/drivers etc as each of the win7 machines.

I am not a networking IT expert.. just a competent user who has done home and work networking as part of everyday computer usage for years, so this is obviously frustrating.

I've touched on all the options I've tried in the previous posts, and the setups involved, so I totally don't know.

The win 7 machine that works, simply had to enable network discovery, and worked. The other two did not.

Why? no idea... how to fix? still no idea.


Steve.

 

[chev65]

The only thing I can think of is that the other Windows 7 machines are mistakenly using Homegroup instead of either workgroup or public for file sharing. Also use either workgroup or public file sharing on all machines, you might have better luck using public file sharing on all the Windows 7 machines.

Also, make sure that all machines are using the same name for the network, the network naming all need to be named workgroup or msgroup or what ever name you choose, needs to be the same for all machines.

Also make sure that all your machines are using different names, they can't all be called tom's pc, each machine needs it's own name or they won't show up at all, yes I have tested this.

 

[iguana]

Yea,..

early on I made sure that every computer on the network is using the workgroup setup, with the name "WORKGROUP".

All the machines have unique names, ie: MIKE-pc, IGUANA-pc, DAVE-pc etc.


just can't believe none of the generous suggestions has worked, and I spent a lot of time before trying everything I could think of.

I might get the IT guy to take all the machines off line, restart everything, flush the router, the switches etc...

I just don't understand why one win7 can see everything and the other two can't, with the exact same setup.


Thanks for your suggestions.


Steve.

 

[iguana]

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.

 

[Zardoc]

I was pretty sure it was a master browser issue. It's just a needle in a hay stack. Sometimes you have to restart from scratch. Takes some time but when added up, I bet it took less time than all the running around.

 

[Zardoc]

I've been sharing with my XP machine since Jan. and never had a single problem so unless something is blocking network access like a third part firewall there is nothing more you can do. The only thing I can think of is that file sharing isn't properly enabled on the XP machine. That was the only thing I ever had to do.

You shouldn't need to do any of the steps shown here today to gain simple file access from your Windows 7 machine to your XP machine. Both Public file sharing or Workgroups should be working for you without having to do anything other than the check list I already posted. Something other than Windows is preventing you from gaining access.

Chev I loved your relitivity on things, I tried to it hat way when I lost my Xbox Media Center connection from my PC. I tried everywhich way I could. The only solution was a rollback. Yet, all it needed was a code. Niet nothing.

Man that is frustrating.

Good for yoy Steve.

 

[drvic10k]

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

 

[chev65]

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. :sarc:

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.

 

[blade1269]

Hey,

hope this helps

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

 

[iguana]

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.

 

[arryo]

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

 

[arryo]

anyone?