Forum Home
Press F1
Thread ID: 138509	2014-12-10 21:16:00	Computer disappears from network	rossnixon (584)	Press F1

Post ID	Timestamp	Content	User
1389936	2014-12-10 21:16:00	I have a LAN of three computers: XP, Win7, Win8. All on fixed IP addresses. Not using HomeGroup at all. After large file transfers, the XP computer can no longer see the Win7 computer, but can see the Win8 computer. Both the Win7 and Win8 can see the XP. The XP can still ping to the Win8 successfully. I have tried enable/reenable the NIC in the XP and the Win8, but no good. It isn't the ethernet switch, as I have swapped out the 10/100 for a GbE. The only fix found, so far, is rebooting the Win8 machine. What can I try next? Another NIC in the Win8 machine? Or something else first? Thanks.	rossnixon (584)
1389937	2014-12-11 02:51:00	That's slightly confusing the way you have written that ?? the XP computer can no longer see the Win7 computer, but can see the Win8 computer. XP can still ping to the Win8 successfully The only fix found, so far, is rebooting the Win8 machine. Errrrr so you can see Win8 and ping it Ok so no problem there -- Doubt its W8 that's the problem with XP not being able to see W7 ( which is what you have written), more likely the XP computer. See if this does any thing ---- Have a look under the network setting/properties, does XP have TCP/IP V6 ticked or even available ? If V6 is there, untick it (on XP) Also on W7 & W8, is network discovery turned on ? When the PC ( which ever one it actually is) :) drops, what is the transfer, EG: W7 or W8 to XP, W7 to W8, XP to either one of the others etc.	wainuitech (129)
1389938	2014-12-11 03:19:00	That's slightly confusing the way you have written that ?? Oh, let me try that again. When the XP machine (PC6) can no longer see the Win7 (PC1) machine, it can still ping to it successfully, but can't open anything via UNC path. Typing \\PC1 into a Run command or Windows Explorer path returns error instead of the shares that PC6 should be able to see. The last 4 mentions of Win8 in my first post should be Win7, sorry.	rossnixon (584)
1389939	2014-12-11 04:25:00	Try using \\192.168.1.5\sharename instead, does that work?	Chilling_Silence (9)
1389940	2014-12-11 04:44:00	Since the only way XP can see W7 ;) is by rebooting W7, when it drops from XP, Can W8 still see W7 or is it only XP that cant see it ?	wainuitech (129)
1389941	2014-12-12 05:19:00	Since the only way XP can see W7 ;) is by rebooting W7, when it drops from XP, Can W8 still see W7 or is it only XP that cant see it ? When XP can't see W7, it can still see W8. And W7 can see both still. And W8 can see both still. Today I copied 1.5GB from W8 to XP. All still OK. Then I copied 1.5GB from W8 to W7. Now XP can't see W7, as usual W7 & W8 can see both machines. I attach screenshots from UNC and IP path to shared drive attempts. Plus I tried a NetScan program. The properties of W7 show no shares when views from XP.607760766078	rossnixon (584)
1389942	2014-12-12 08:59:00	Well there's yur problem... 2 machines with the same hostname.	fred_fish (15241)
1389943	2014-12-12 09:08:00	Well there's yur problem... 2 machines with the same hostname. :thumbs::thumbs: Yep that should be it, you cant have two (or more) computers on the same LAN with the same name.	wainuitech (129)
1389944	2014-12-12 09:33:00	:thumbs::thumbs: Yep that should be it, you cant have two (or more) computers on the same LAN with the same name.No, WORKGREAT is my network name, in place of the default name of WORKGROUP. It isn't the computer name. Those are PC1, PC4, PC6. I think the NetScan program could be using confusing headings.	rossnixon (584)
1389945	2014-12-12 09:41:00	No, WORKGREAT is my network name, in place of the default name of WORKGROUP. It isn't the computer name. Those are PC1, PC4, PC6. I think the NetScan program could be using confusing headings. Well, "Hostname" seems pretty clear.	fred_fish (15241)
1 2 3