Curiouser and curiouser (haven't been able to test your fix, Greg, as it needs to wait until after business hours.)
Owing to our network structure, our hosts have the following records available: SERVERNAME SERVERNAME.domainname.usc.edu (aka FQDN) SERVERNAME.usc.edu Mapping shares remotely using SERVERNAME or SERVERNAME.FQDN works. Using SERVERNAME.usc.edu doesn't... -----Original Message----- From: Greg Olson [mailto:gol...@markettools.com] Sent: Wednesday, April 14, 2010 2:38 PM To: NT System Admin Issues Subject: RE: Server 2003 cannot map it's own shares IP Nat running by any chance? I was also getting such kind of message i try to follow the below steps:- 1. Right click on My Computer, and then click on Properties. 2. Click on Device Manager, by going through Hardware Tab. 3. On the View menu, click on Show hidden devices. 4. Now expand Non-Plug and Play Drivers, right-click on IP Network Address Translator, and then click Disable. 5. Now finally click Yes to restart the computer. -----Original Message----- From: Salvador Manzo [mailto:ma...@usc.edu] Sent: Wednesday, April 14, 2010 2:16 PM To: NT System Admin Issues Subject: Server 2003 cannot map it's own shares 2003 SP2 Standard Per the subject line, I have a machine that is both a web and file server that receives a System Error 67 when attempting to connect to shares it hosts. Of course, the applications it hosts require access to local content using UNC paths, so they won't load. Google has so far been less than helpful. Anyone ever seen something like this or have some tips? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
