Server 2003 network directory access

[Guest Hybrid]

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?

[Guest Pegasus \(MVP\)]

Re: Server 2003 network directory access

 

 

"Hybrid" <j.doe@nospam.com> wrote in message

news:%23iOt2yUhIHA.4744@TK2MSFTNGP06.phx.gbl...

>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?

 

This sounds like a compromised server. If it was my server

then I would rebuild it from the most recent backup.

[Guest lforbes]

RE: Server 2003 network directory access

 

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?

>

>

>

[Guest Bill Board]

Re: Server 2003 network directory access

 

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?

 

"lforbes" <lforbes@discussions.microsoft.com> wrote in message

news:585A249A-9DE5-49EE-A5F8-3E8FD540CAF2@microsoft.com...

> 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?

>>

>>

>>

[Guest Bill Grant]

Re: Server 2003 network directory access

 

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.

 

"Bill Board" <John.Doe@NoSpam.com> wrote in message

news:u72m1rejIHA.1168@TK2MSFTNGP02.phx.gbl...

> 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?

>

> "lforbes" <lforbes@discussions.microsoft.com> wrote in message

> news:585A249A-9DE5-49EE-A5F8-3E8FD540CAF2@microsoft.com...

>> 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?

>>>

>>>

>>>

>

>

[Guest lforbes]

Re: Server 2003 network directory access

 

Hi,

 

That is the DNS name of your domain. I use mydomainname.local but some use

..com. However, .local (internal only DNS extension) is recommended over an

external DNS name that can cause issues.

 

Domains in NT did not use DNS. Therefore they only had one name - a netbios

name. Eg. Lake

 

Domains with Active Directory (Windows 2000, 2003, 2008) are DNS domains and

therefore need an extension (dns name).

 

Eg. lake.local

 

Therefore you would map \\fish@lake.local\programs$

 

If you don't know what your extension is then open up Active Directory or

DNS and the name will be right there.

 

Cheers,

Lara

 

"Bill Board" wrote:

> 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?

>

> "lforbes" <lforbes@discussions.microsoft.com> wrote in message

> news:585A249A-9DE5-49EE-A5F8-3E8FD540CAF2@microsoft.com...

> > 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?

> >>

> >>

> >>

>

>

>

[Guest Paul Adare]

Re: Server 2003 network directory access

 

On Mon, 24 Mar 2008 20:22:01 -0700, lforbes wrote:

> Domains in NT did not use DNS. Therefore they only had one name - a netbios

> name. Eg. Lake

>

> Domains with Active Directory (Windows 2000, 2003, 2008) are DNS domains and

> therefore need an extension (dns name).

>

> Eg. lake.local

>

> Therefore you would map \\fish@lake.local\programs$

>

> If you don't know what your extension is then open up Active Directory or

> DNS and the name will be right there.

 

The point is that what you've typed above is not a DNS name but is an

RFC822 formatted name. The DNS name would be \\fish.lake.local\program$.

 

--

Paul Adare

MVP - Virtual Machines

http://www.identit.ca

If a program is useful, it must be changed.