PC1 not showing up under "Network" on Laptop-X (only)

[dahaiou]

All nodes mentioned here are running Win7 32bit.
CORRECTION - Sorry, that was inaccurate:
- PC1 has Win7 Professional 32
- Laptop-X has Win7 Home Premium 64
- Other nodes have Win7 or Vista, 32 or 64

We have PC1 acting as fileserver in a local network at the office.
PC1 has fixed IP 192.168.1.12. Directory \\PC1\netdir is exported and other PC's connect to it as a network drive.

But from this one laptop, Laptop-X, PC1 simply does not show up among the nodes under "Network" whatever I do.

From Laptop-X I can ping PC1 by name or by IP. OK result
From Laptop-X I can remote connect (RDC) to PC1 by name or by IP. OK result
However, from Laptop-X I cannot connect disk M: to \\PC1\netdir, neither in the file explorer or by "net use" command. The double backslash node name \\PC1 is simply not visible to Laptop-X.
(As those of you who have been around the block have already guessed, Laptop-X happens to belong to the one person with the biggest need for this connection)

I have tried:
- turning the firewall and other protections off
- Connecting Laptop-X over Wifi as well as cable
- Checked workgroups. Yes: Laptop-X is set to the same workgroup as PC1.

From any other PC in the network, \\PC1\netdir is visible under "Network" in the file explorer and can be connected as a network drive with no problem.

Any pointers on what to try next would be appreciated.

 

[2xg]

Hello,

Instead of trying to access the computer name please try the IP address of the file server.
From any computer that you need to access PC1, click on Start and type \\PC1\192.168.1.12 and press enter.

However, from Laptop-X I cannot connect disk M: to \\PC1\netdir

An update will be nice.

 

[dahaiou]

I wrote \\192.168.1.12 in the search input field attached to the start menu.

Result:
Error code: 0x800704cf - Cannot connect to network location

What is interesting is that this code is different from what i get if I input nonsense there:
\\nonsense-name -> Error code: 0x80070035 Network access path not found

So, no progress as yet. I would still appreciate pointers on how to start fencing this fault in and then home in on a solution.

 

[dahaiou]

Update: Tried these commands:

net view -> Result: empty output

nbtstat -n -> Result: Only the own node is seen

 

[2xg]

Can you please do a test? From the file server try sharing an entire drive (C or D drive), call it Test Drive for now and give it full permission. Now try accessing the test drive, click on start and type \\192.168.1.12\Test Drive then press enter after. Where you able to access it this time?

Also, what type of Security Software do you have installed from the file server and the computer that can't connect to it?

 

[dahaiou]

Thanks for the suggestions. It suddenly started working, but I have no idea why.

This means I cannot carry on troubleshooting to get to the bottom of it, because
the trouble is no longer there to be shot at.

I feel cheated in a way, but I shouldn't complain. In another way it's a relief to have this
particular pain in the butt out of the way.

I'll check in again if the fault reappears.

 

[2xg]

If it ain't broke, don't fix it.

Thanks for the update and good to hear all is well again.