matthewadams
New member
Hi,
Windows Server 2008 noob. I have a basically stock Windows Server 2008 Standard standalone installation (with no domain controller), then added TFS 2010. Now, I'm running the TFS Build Service for continuous integration, which requires builds to use a UNC path-based drop folder, not a drive-letter-plus-folder path. I created a folder C:\Builds and then shared it as Builds, granting "Full Control" permissions to the account the build service runs as at both the share & NTFS permission levels.
When logged in to that machine as the build server account (or any other administrator account, for that matter), start Windows Explorer and try to navigate to \\myserver\Builds, I get an error stating "The network path was not found". I've tried it with Windows Firewall both on & off with the same result.
I have no network-related issues that I know of. I can access any remote website without a problem, and I can access various network-based services (like TFS) from remote computers just fine.
BTW, I've also tried accessing the share as \\127.0.0.1\Builds, \\localhost\Builds, and \\.\Builds (last one just for fun) and they all throw errors.
What do I need to do in order to use a UNC path on the local machine?
Thanks,
Matthew
Windows Server 2008 noob. I have a basically stock Windows Server 2008 Standard standalone installation (with no domain controller), then added TFS 2010. Now, I'm running the TFS Build Service for continuous integration, which requires builds to use a UNC path-based drop folder, not a drive-letter-plus-folder path. I created a folder C:\Builds and then shared it as Builds, granting "Full Control" permissions to the account the build service runs as at both the share & NTFS permission levels.
When logged in to that machine as the build server account (or any other administrator account, for that matter), start Windows Explorer and try to navigate to \\myserver\Builds, I get an error stating "The network path was not found". I've tried it with Windows Firewall both on & off with the same result.
I have no network-related issues that I know of. I can access any remote website without a problem, and I can access various network-based services (like TFS) from remote computers just fine.
BTW, I've also tried accessing the share as \\127.0.0.1\Builds, \\localhost\Builds, and \\.\Builds (last one just for fun) and they all throw errors.
What do I need to do in order to use a UNC path on the local machine?
Thanks,
Matthew
