• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

windows 2k3 file sharing

groovin

Senior member
im playing with win2k3 server and trying to set up a few shares on it to move some data over... i shared a couple folders by right clicking and then going to sharing... but when i try to access the server from a client (tried win2k and winXP clients) i get an error saying "Server is not accessible. You might not have permission to access this resource." the server is part of a domain and all computers that are trying to access it are part of the domain.

the firewall is off, i can ping and even VNC into the server... just cannot browse its shares!

from the server, i can browse other windows servers and network shares (even my own) just fine.

did i miss something glaringly obvious? this is my first real crack at win2k3 so perhaps i did miss a detail?

Thanks
 
Did you set share permissions AND file system permissions that allow your remote user to access those files?
 
What I typically do is set Share Permissions: Full Control (or "Authenticated Users" in a mixed-mode domain) and then the appropriate NTFS permissions to allow the user to access the files/directories.
 
ok set those on the shares and still having problems. let me clarify something, i see the server in net'hood, but i cannot access it to see the shares... when i click on the server, it stalls for a bit and then returns that error message.

thanks again
 
well it turns out its not a perm problem after all... when i switch back to DHCP, everything works fine. but when i give it an IP, say 192.168.1.100 then the errors come back. When it has a static IP, I cannot ping it by network name... for example 'ping SERVERNAME' says "pinging SERVER [192.168.1.203]' but i have set the IP manually to 1.100... no idea why the other machines want to ping 1.203... i even set it back to DHCP (it grabs ip 1.203) and released the IP and then tried again... but other machines still try to ping 1.203... im guessing that's why file sharing is failing... because all htese clients for some reason think the server is at 1.203 when its at 1.100... but when i use DHCP... everything works...

anyone come across this before?
 
Back
Top