Hi, I have a network with 5 PCs, that use an app that runs on a separate PC (server). Each PC has access to shares on the Server PC. I had to swap out the Server PC recently because it required a major hardware facelift, and now, even though i have given it the exact same PC name and IP, no other PC can connect or even see the new Server's shared folder via My Network Places. The PC has Simple File Sharing disabled, and has allowed permissions to these folders (even the entire C drive) to EVERYONE, with full access rights. Any suggestions?

Same workgroup name? Can you access shares via \\ip address\share name or map using ip and different name? I read it wrong and answer it wrong too. So get off my case you goober.

First, make sure Windows firewall or any other firewalls are turned off. The see if one of the client computers can ping the server computer. Then report back. Assume that I already did an Internet search.

Hi, ok heres the status. I setup this LAN and it was working great, until: I introduced a new PC into the LAN giving it an ip (192.168.100.200) and name PC1. All other PCs on LAN could access this PCs shares, no prob. I then had to give this PC a new name and IP as it would now replace an existing Server on my LAN. So, i gave it identical details as the server, i.e. 192.168.100.101 and name server. I obviously powered down the old server before switching on the new server to avoid IP conflicts. Since this change, i cannot access the shares on the new Server. I CAN ping ok, and i CAN see the new server PC in my workgroup, but if i double click it to view the server's shares, it comes back with an Access denied message, saying permissions aren't set on the server PC to allow this connection. I have re-checked settings and permissions, and shares on the new server and all is ok. Could it be a glitch caused by how i've named two PCs on the same LAN with same names/IPs? If i switch off the new server and switch on the old server, the shares to the old server work fine. Its clearly a prob with the new server PC. Someone mentioned i should install the NWlink IPX protocol on my LAN interface, which i did, but to no avail. Please help someone. This seems more of a windows glitch/bug as a consequence of naming and renaming a PC on a LAN on various occassions.

Please help...........someone

1. If it is Windows XP Pro with SP2, you have to have passwords on the accounts your using to access the shares. It is a new thing in SP2. If the account has a blank password, then create a password. 2. On whatever client computer you're using to access the shared folders on the server computer, you should be logged into the client computer with an identical username and password that exists on the server computer. The server computer doesn't have to be logged in with that username and password, but on the client you need to be logged with an identical username and password, and that username needs rights to that shared folder. Give this a run and see how it works. Good luck. Assume that I already did an Internet search.

Analyst - Super! I actually tested that this morning to cancel that out of my list of possible causes. So you say it is a new thing in SP2 that the uer needs to exist on the server to enable viewing of its shares? Man, its kept me busy for a bunch of hours this. Thanks alot for you feedback anyway pal, much appreciated.