Remote Support Software

Provide instant remote support to customers and employees:

Click here for a free trial

Error 0x80070035 when trying to connect to network share using cname fqdn on windows 2008 r2 server

Hi,
I applied KB
http://support.microsoft.com/kb/926642
and yet, I cannot access any network shares using the FQDN of the server, which happens to be a cname alias.
I also looked at all the spn records and both the cname fqdn and netbios names exist in the list.

ther server is an windows 2008 r2 x64 with SP1.

Any suggestions?

thanks!
-sul.

There is an amazing pack of free network admin tools. click here to download it






June 7th, 2012 7:29am
update:
I have changed my dns name to an A record on the DNS. I restarted the server and yet, I cannot connect to any network share using the FQDN of the server from the server itself. I can connect from a remote machine just fine.

any help is appreciated,

thanks!
-sul.

There is an amazing pack of free network admin tools. click here to download it






June 7th, 2012 9:55am
Hi sul,

Thanks for posting here.

Which method that descripted in KB 92662 did we applied to this Windows Server 2008 R2 host ? and what was the error prompt when attempted to access this server via its FQDN ?

> I restarted the server and yet, I cannot connect to any network share using the FQDN of the server from the server itself

Have we tried to first clean local DNS cache and verifying the resolution by nslookup ?

If we can access form other computers with other OS but itself then Id suggest to first restore the changes we made before on Windows Server 2008 R2 and try the solutions in KB 281308 and see how is going:

Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name

http://support.microsoft.com/kb/281308/


Thanks.

Tiger LiTiger Li
TechNet Community Support

Need to support users over the internet? click here try our remote control online beta






June 11th, 2012 12:16am
Hi Tiger,
it turns out that there was a stale entry in the ../system32/drivers/etc/hosts file that was causing this behavior. Apparently, the fqdn was resolving to an invalid IP address listed on the hosts file. Once I removed the entry, the issue was resolved.


Thanks!
-s.

There is an amazing pack of free network admin tools. click here to download it






June 11th, 2012 8:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics