Poof!!...they're gone

My first move would be to reboot every machine on the network and allow them a chance at rediscovery.

detailer said:

Hi everyone-first snag on my one year trouble free home network.Using a Linksys router to connect two XP's,and three 7's,oh,and a printer.This set up without a hitch,despite all the horror stories about XP's "seeing and talking to" 7's.Suddenly,yesterday,one of the 7's (a Lenovo notebook) was unable to locate either of the XP's on the network map.Funny thing though-both XP's were able to "see" and retrieve files from the Lenovo.Strange indeed.Since I never had any success with Homegroup,having them all "talk" to each other on my network (MSHOME),I was perfectly happy.I've checked every service and setting I can think of,but to no avail.If this helps,the only strange things I see are,(1) the network discovery type for the Lenovo is WSD,where all other devices on the network are SSDP,and (2),the Lenovo shows the IP that it acquires from my workplace(127.0.0.1),instead of the usual 192.168.blah.blah associated with the Linksys router.Though it does connect to the internet and "see" the other 7's when I'm at home.Any ideas? I'm not a network guy,and just stepped in $hit when this all came together for me last year.Lucky then,but not smart enough to fix it now.Googled and read til my head hurt yesterday.Thanks for the read!

Seems like the Lenovo is still using the workplace IP or default gateway from work rather than the one at home. It might help to go "manage wireless connections" and delate the old credentials then set up the connection again.

Have you checked the ipconfig /all on the Lenovo to make sure your on the same subnet and using the same default gateway as your other machines at home?

If you aren't sure it would be helpful if you can post the ipconfig /all here from one of your home machines and the Lenovo.

If you are going between two subnets it sometimes helps to list them both in the advanced TCP/ip properties window.

Oh and the reason the Homegroup didn't work was because you have XP machines in the network. Although it is possible to have a workgroup running along side a Homegroup it's easier to just set up a Workgroup in most cases.

detailer said:

At work right now-seems the ipconfig run from the console (of the Lenovo) yielded the dreaded "media disconnected". Another Google adventure that led me nowhere.I've been showing that 127 IP at home for weeks,but since I still had connectivity (to the web) and no free time,I let it slide.Sorry,not sharp enough to know what you mean by "deleting credentials".Networking is mind boggling for me,so non-computer speak would be appreciated wherever possible. I'll go the re-boot all devices route when I get home.Posting from work now so I have some "ammo" to use at home tonight. Thanks for the replies thus far!

Delating the old wireless network credentials is about the easiest thing you can do.

Just go to the network and sharing center, look to the left collum and choose "manage wireless connections" then find your credentials and delate them then set up a new wireless connection and make a new one making sure to input the correct info "what ever you have set up for your routers wireless settings" like WPA2, the correct SSID, type of connection like wireless N and so forth.

It's not about to work with the rogue 127 IP it has now when your Home gateway is using the standard 192.168.x.x default gateway. This would be easier if you were at home on the machine in question of course.

Also if you need to work between two different subnets it may help to set up the different subnets in your TCP/ip properties window.

detailer said:

Yeah,I'll try that when I get home-lost me on the sub-net mask thing though.Also seeing from the console command ipconfig /all that DHCP is not enabled,but when I go to wireless properties/ipv4 properties both of the radio buttons are checked for auto discovery.It just gets better,huh?Best to continue later on at home,but all replies cheerfully accepted throughout the day

It may seem complicated right now but once I see the ipconfig and you make a few adjustments to the wireless credentials it should be ok.