+ 1 Votes Wow, I can't access it either.... Tony Hopkinson 2 years ago Take some deep breaths, start at the beginning.... + 0 Votes Fix Registry elibarikikilewo 2 years ago Haha!.. all i had to do was buying a Registry Cleaner software online and did a full scan after installation >> then fixed errors>>..then DANG!..>> Haha!.. Am laughing ain't i?.. + 0 Votes Windows headaches oldbaritone 2 years ago Windows does some behind-the-scenes user access nonsense, and sometimes it can create headaches. You think you are logging on with a set of credentials, but Windows decides to use something else instead. This is particularly true if the password for your userid is different on the remote machine than on the local machine. One work-around I have been able to use sometimes is to access the same server using its IP address: If "myserver" is at address 192.168.1.100, then it may be referenced either as \\myserver\ or \\192.168.1.100\ sometimes this will give you a second chance at the access restrictions. Also, since you said access has been granted to "everyone", use credentials for a different user on the remote machine, e.g. if you are signed on your machine as "user_a" try the "connect as different user" option and specify "user_b" for the remote machine. Finally, I have also had problems with a password mistake when accessing remote machines. You put in a different password the second try and it doesn't work. When all else fails, reboot and try again. Oh, and did I mention, "when all else fails, reboot and try again." and if that doesn't work, try rebooting. + 0 Votes check your windows firewall - wscui.cpl danekan 2 years ago outside of the obvious of trying \\192.168.0.5 or whatever ... does the windows machine itself have "File and Print sharing for microsoft networks" checked/enabled for the network adapters? (under network connections, right click your network adapters and go to properties and verify) also, if i recall correctly, XP SP2 had some weird new firewall limitations that blocked a lot of stuff by default. Namely, I think by default the firewall blocks incoming Fire/Print sharing and you have to explicitly go in and modify the firewall policy to allow it, under the Exceptions tab. run wscui.cpl and check. You'll also need to add exceptions for the ports that SQL server uses. Though personally, I would outright disable Windows firewall at least until you've verified everything as functional. I feel like in SP3 they rolled back some of the firewall restrictions (also, is there a reason you aren't running at least SP3?) (And uhh, you're running a production SQL server on a windows XP SP2 box? ...for a business?) + 0 Votes Fix Registry elibarikikilewo 2 years ago Haha!.. all i had to do was buying a Registry Cleaner software online and did a full scan after installation >> then fixed errors>>..then DANG!..>> Haha!.. Am laughing ain't i?..