Issue with UNC access to a server

Win 2008R2 server on the our network allows RDP access with the administrator UN and PW but when I UNC I can't get access.
The server is NOT on the Domain, so I use the \administrator switch. No dice.

I do get prompted for credentials, but it never accepts the UN &PW.
This server is on a diff subnet to me but when I try access it from a machine on the same subnet I still get the
'not accessible' message.
LVL 1
wannabecraigAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wayne88Commented:
Did you enable RDP on the server?  If yes, also select "Allow connections from computers running any version of Remote Desktop" to ensure that there will be no issues when you use older RDP client.  If this server is not internet facing then no worry.

https://technet.microsoft.com/en-us/library/cc794832(v=ws.10).aspx

If RDP is enabled and you have given the selected user to allow to remote in then it should work without issues.  When you say the server is not accessible, did you get the login prompt?
0
wannabecraigAuthor Commented:
RDP works, that's not the issue, running from UNC path doesn't.
0
Wayne88Commented:
Ok, when using the machine on the same subnet as the server and you use UNC you mean using the machine name right?  Let's try two solutions:

1.  Try adding the server to the DHCP reservation list even if server is not part of the DHCP range.  This way the DHCP server knows there is a machine with that name and associated IP address.

2. If you add the server name and IP address to the host file of the machine you're trying to connect from does it work?  If yes then DNS is the issue.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Fred MarshallPrincipalCommented:
Do you mean UNC with \\[servername] or \\[ipaddress] ?
0
wannabecraigAuthor Commented:
I mean IP.

So it's \\192.168.1.5\c$

Apologies, for the confusion
0
Fred MarshallPrincipalCommented:
What about \\192.168.1.5\c  ??  i.e. without the "$" ?

How is sharing and security set up for "c"?

The login could be different than for RDP (but in saying that I'm not saying that it can't also be the same).  That is, there can be different login credentials that can work.
0
Fred MarshallPrincipalCommented:
C$ is somewhat a strange beast.  It's not recommended that it be shared in the first place for rather obvious reasons.  That said, I have situations where it's done.  

In the dim past, I did some work to assure that it would work and, as I recall, the treatment was a bit different than for any other folder.  I'd have to dig it all out as I have forgotten much more than I know.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.