• 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.

Network drive access problem.

PlastikSpork

PlastikSpork

Member
When I connect to my server via the IP address \\192.168.1.3 I can access all shared network drives and have full control.

When I connect to my server via the computer name \\mediaserver-pc I can see all three drives. I can access 2 of the drives read only and one of them I get an error "Windows cannot access \\mediaserver-pc\seagate2T You do not have permission to access"

what am I missing here? I've always just used the IP address so this is the first time I've run into this issue.
 
That's pretty wierd. There shouldn't, to my knowledge, be any difference in terms of access permissions, depending on whether or not you access a server via DNS/UNC name, versus IP address.

Sure you don't have two servers, and are confusing them?
 
VirtualLarry said:
That's pretty wierd. There shouldn't, to my knowledge, be any difference in terms of access permissions, depending on whether or not you access a server via DNS/UNC name, versus IP address.

Sure you don't have two servers, and are confusing them?
Click to expand...

Yeah I only have one server... I find it pretty weird myself.
 
Update: I just changed the name of the "Seagate 2T" drive name to "Seagate2T" by removing the space. Now I am able to connect to this drive as well but only as read only just like the other two drives. I also tried to mount the drive using the Net Use command with the same results.
 
What I do at home, in my windows environment, is to remove all shares for EVERYONE, and add a user log in share (typically the one I use to log into PC), and that forces me to log in, OR auto logs in (if both pc's have the same permissions)...usually gets around these flakey issues.
 
ViviTheMage said:
What I do at home, in my windows environment, is to remove all shares for EVERYONE, and add a user log in share (typically the one I use to log into PC), and that forces me to log in, OR auto logs in (if both pc's have the same permissions)...usually gets around these flakey issues.
Click to expand...

I tried removing EVERYONE from the shared list with no luck... If I did that I couldn't access the drives at all. When I added back EVERYONE and gave full control to everyone then I was able to access the drive with full control. Even after removing EVERYONE and then mounting that drive with different credentials forcing it to use my log in and password I still wasn't able to access the drive.

It seems like when I use the IP address it uses the advanced file sharing method and when I use the computer name it uses the simple file sharing method.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top