|
Posted by Bill Grant on March 24, 2008, 7:38 pm
Please log in for more thread options Do you really have a single label domain, or are you just giving us the
Netbios name of it?
Using a single label domain is not recommened for W2k/W2k3.
> I've never seen the \server@domain.local\share what would I put for the
> .local part?
>
> For example if my server was called fish and the domain was called lake
> and my share was programs$ i'd enter \fish@lake\programs$
>
> Is that correct?
>
>> Hi,
>>
>> Remember using share names like \server\share don't use DNS but NetBios.
>> Try \server@domain.local\share instead. Does that work?
>>
>> If so there is something up with the NetBios. Usually it has fallen out
>> of
>> the NetBios list on the Master Server.
>>
>> We have always had NetBios issues. We use WINS but even that isn't 100%
>> foolproof.
>>
>> "Hybrid" wrote:
>>
>>> I 've had many issues with a server over the past couple of days. The
>>> server is running Windows 2003 Enterprise and handles our backup-to-disk
>>> operations. Over the weekend, a memory module failed and the server
>>> restarted. When we booted back up on Monday, there was corrupt data
>>> that
>>> was saved to the hard drive. The first thing we did was test to ensure
>>> that
>>> there was no issues with the hard disk and after verifying it was the
>>> memory, we removed the bad module and began to repair the problems.
>>>
>>> There were a couple of corrupt OS files keeping the server from booting
>>> so
>>> we recovered those in the recovery console and it booted into windows
>>> fine.
>>> The next problem we ran into was the network card showed that the driver
>>> could not be loaded becase a file was missing and would not show the
>>> network
>>> connections. This turned out to be something that was corrupt in the
>>> registry and after resolving it using MS article KB825826, we were able
>>> to
>>> assign the network card it's TCP IP info. This is where we got stuck.
>>>
>>> This server is not a domain controller. It can ping other computers on
>>> our
>>> network by their host names using the assigned DNS servers. Other
>>> computers
>>> can also resolve its host name. The problem occurs when I try to access
>>> any
>>> computer shares over the network. When I type
>>> \computer_name\share_name\
>>> I get "The network location cannot be reached. For information about
>>> network troubleshooting, see Windows Help". If I'm on the backup
>>> server,
>>> when I type \backup_server\share_name\ I get
>>> \backup_server\share_name\ is
>>> not accessible. You might not have permission to use this network
>>> resource.
>>> Contact the administrator of this server to find out if you have access
>>> permissions " I've checked the to make sure all sharing and security
>>> permissions are set correctly. Furthermore, if I am on any computer on
>>> our
>>> network and I try to access \backup_server\share_name\ I get "The
>>> network
>>> path was not found"
>>>
>>> What else is strange is that Symantec Backup Exec System Recovery, which
>>> uses file shares, can access the backup server shares from other
>>> computers
>>> to perform it routine backups.
>>>
>>> Does anyone have any ideas?
>>>
>>>
>>>
>
>
| 
XML Sitemap