All of the computers here are connected to the server. With the ones I've tried, I can access the server via:

My Computer -> My Network Places -> Entire Network -> Microsoft Windows Network -> [servername]

I can then see all of the computers connected to the server but importantly, I can access folders on the server. With one computer, I cannot do this. If I follow the above links, it takes me to the server folder but the folder only has Printers&Faxes icon inside.

The software can see the server, and I can access the internet, but I cannot see server folders. This means I cannot do a client install of a software on the computer.

Any ideas?

I've tried changing the switches the computer is connected to on the network but this makes no difference.

I also cannot see a shared network drive either. What am I doing wrong?

Have you tried logging in with a domain administrator account?

Don't have one (or I've not been told it, which is a pain if I'm the "system administrator"). I use the same generic log on to get into Windows but then all medical programs have individual log-ins. We don't have roaming profiles either.

This one computer was a "spare" that was laying about so I swapped it for the one that didn't work. Connected to the network fine and has been running one medical program without issues. The boss wants a second medical program on there and I have to do a client install. Part of the issue is that the computers are PCT property so I imagine they would have the admin password!

I asked because it's odd to see the printers but not the folders. That sounds like a permissions problem, but if the same "generic" domain login works OK on the other computers, then it seems sell likely.

Is "Client for Microsoft Networks" ticked in the network connection properties?

Also check the DNS is the same as the other machines - I imagine it will be using DHCP so that should be fine, but worth a quick look to check.

Beyond that, all I can suggest is typing the full network path into the address bar. For example \\servername\sharename\

Yes to client for networks. Also checked file and printer sharing in MS firewall exclusion (although firewall is off by default). Netbios is active in services.msc.

Tried to access \\servername which doesn't work (not recognised) but works on the other computers. Very frustrating and I suspect it's something to do with some settings somewhere.

Checked TCP/IP settings - turns out it was automatic and I know that all computers here have it all configured manually. Once I'd set it up right, it seems to be working so far *fingers crossed*. I was able to see the server and the folders within. Currently running the client install program right now.

*hits head*

Everything was working fine but decided to reboot the computer after some software updates. Now can't log on to computer! talks about "doman controller" being unavailable!

If you can't log in, the only thing you can check is the physical connection. On your DHCP server, can you see an IP address issued to the PC? If so, can you ping it?

If it's not talking on the network, then perhaps that's why it was in storage? Intermittent hardware fault?

If I yank out the network cable, I can log on. IIRC this is to do with local profiles. How can I get it to always use a local profile?

I think the machine was a spare in storage rather than just put into storage. Any problematic computers eg failed HDD get reported to the PCT who come and take the machine away and either repair and return or provide a new machine.

I can ping it without any problems too.

I can't see any problems on the server computer. I might try deleting the computer and re-adding it. Tomorrow. Too tired today.

It could be that the machine name isn't registered on active directory, but it was when the PC was originally configured. That's why the off-line version works.

On the server, open "Active Directory Users and Computers" in "Administrative Tools".

You'll see the PC's that are authorised for the domain listed there.

:EDIT:

Maybe it's just spelled wrongly?

How long was it in that cupboard for?
The message didn't say anything about losing its trust relationship with the domain controller by any chance?

Don't know about duration.

What's frustrating is that I've had a fresh look at things today. The subnet mask was 255.255.255.0 - I changed this to 255.255.255.192 and it then tells me I have a duplicate computer on the network. I had a look netscan tells me there are two computers with the same ID on two different IP addresses. In the admin controls on the server, there's only one computer authorised.

The practice manager isn't here so can't tell me where the previous computer went - I suspect it was repaired and put back into service. I need to try and track down this duplicate computer.

I have found the conflicting computer - belongs to one of the bosses and has never been moved/changed AFAIK. I have changed the computer name and added it to the domain controller. Still can't log on to the computer because of domain controller error message.

Any ideas? Suspect I've done something wrong in adding the computer.

EDIT: I've discovered that both computers have the same service ID tag and computer name. I suspect one was a replacement for the other at some point. I can't edit the service ID tag in BIOS.