\\servername\sharename is unavailable

[Guest V&B]

Lately we get the problem on our server that it cannot reach the backupserver

by \\servename\sharename, but when we use \\IP-adress\sharename it is no

prblem.

When we ping the backupserver we get the right IP-adres back.

After reboot of the server the problem is gone for a while, but returns

everytime.

We use Windows Server 2003 Standard Edition SP2

 

Harry Veenkamp

Villeroy & Boch Wellness Bv

[Guest Lanwench [MVP - Exchange]]

Re: \\servername\sharename is unavailable

 

V&B <VB@discussions.microsoft.com> wrote:

> Lately we get the problem on our server that it cannot reach the

> backupserver by \\servename\sharename, but when we use

> \\IP-adress\sharename it is no prblem.

> When we ping the backupserver we get the right IP-adres back.

> After reboot of the server the problem is gone for a while, but

> returns everytime.

> We use Windows Server 2003 Standard Edition SP2

>

> Harry Veenkamp

> Villeroy & Boch Wellness Bv

 

Hi - do you use AD? What do you mean by "backupserver" ?

 

Please post an unedited ipconfig /all from your server & the "backup"

server.

[Guest JohnB]

Re: \\servername\sharename is unavailable

 

In what way can it not "reach the backup server"? Browsing in Explorer?

What's the OS of the Backup Server?

 

"V&B" <VB@discussions.microsoft.com> wrote in message

news:7A7FF23A-0C67-4172-BDD6-9E32EAC0853E@microsoft.com...

> Lately we get the problem on our server that it cannot reach the

> backupserver

> by \\servename\sharename, but when we use \\IP-adress\sharename it is no

> prblem.

> When we ping the backupserver we get the right IP-adres back.

> After reboot of the server the problem is gone for a while, but returns

> everytime.

> We use Windows Server 2003 Standard Edition SP2

>

> Harry Veenkamp

> Villeroy & Boch Wellness Bv

>

[Guest V&B]

Re: \\servername\sharename is unavailable

 

 

 

"Lanwench [MVP - Exchange]" wrote:

> V&B <VB@discussions.microsoft.com> wrote:

> > Lately we get the problem on our server that it cannot reach the

> > backupserver by \\servename\sharename, but when we use

> > \\IP-adress\sharename it is no prblem.

> > When we ping the backupserver we get the right IP-adres back.

> > After reboot of the server the problem is gone for a while, but

> > returns everytime.

> > We use Windows Server 2003 Standard Edition SP2

> >

> > Harry Veenkamp

> > Villeroy & Boch Wellness Bv

>

> Hi - do you use AD? What do you mean by "backupserver" ?

>

> Please post an unedited ipconfig /all from your server & the "backup"

> server.

>

>

>

Yes, we use AD.

We use ntbackup to create a backup on the "backuserver".

The server is server 2003, the backupserver is linux.

A kix script makes the drivemapping to right "backupserver"

Here it goes wrong, after a while it cannot connect anymore to the

\\servername\sharename, while \\IP-adres\sharename still works.

After rebooting the server it will work again, but after a period of time

the problem occurs again.

 

Microsoft Windows [Version 5.2.3790]

© Copyright 1985-2003 Microsoft Corp.

 

C:\Documents and Settings\Administrator.PCWNLRICTPROE>ipconfig /all

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : PCWNLRICTPROE

Primary Dns Suffix . . . . . . . : wnl.villeroy-boch.net

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : wnl.villeroy-boch.net

ads.villeroy-boch.net

met.villeroy-boch.net

villeroy-boch.com

 

Ethernet adapter Local Area Connection:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® PRO/1000 MT Network Connection

Physical Address. . . . . . . . . : 00-C0-9F-31-85-86

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 92.0.0.7

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . : 92.0.0.254

DNS Servers . . . . . . . . . . . : 127.0.0.1

92.0.0.26

192.168.166.16

[Guest V&B]

Re: \\servername\sharename is unavailable

 

Yes, we make a drivemapping to the backupserver using a kix script and then

use ntbackup to make the backup to that drive. The backupserver runs on linux.

When testing on the server manual using explorer and typing

\\servername\sharename it cannot open the share

 

"JohnB" wrote:

> In what way can it not "reach the backup server"? Browsing in Explorer?

> What's the OS of the Backup Server?

>

> "V&B" <VB@discussions.microsoft.com> wrote in message

> news:7A7FF23A-0C67-4172-BDD6-9E32EAC0853E@microsoft.com...

> > Lately we get the problem on our server that it cannot reach the

> > backupserver

> > by \\servename\sharename, but when we use \\IP-adress\sharename it is no

> > prblem.

> > When we ping the backupserver we get the right IP-adres back.

> > After reboot of the server the problem is gone for a while, but returns

> > everytime.

> > We use Windows Server 2003 Standard Edition SP2

> >

> > Harry Veenkamp

> > Villeroy & Boch Wellness Bv

> >

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: \\servername\sharename is unavailable

 

V&B <VB@discussions.microsoft.com> wrote:

> "Lanwench [MVP - Exchange]" wrote:

>

>> V&B <VB@discussions.microsoft.com> wrote:

>>> Lately we get the problem on our server that it cannot reach the

>>> backupserver by \\servename\sharename, but when we use

>>> \\IP-adress\sharename it is no prblem.

>>> When we ping the backupserver we get the right IP-adres back.

>>> After reboot of the server the problem is gone for a while, but

>>> returns everytime.

>>> We use Windows Server 2003 Standard Edition SP2

>>>

>>> Harry Veenkamp

>>> Villeroy & Boch Wellness Bv

>>

>> Hi - do you use AD? What do you mean by "backupserver" ?

>>

>> Please post an unedited ipconfig /all from your server & the "backup"

>> server.

>>

>>

>>

> Yes, we use AD.

 

OK.

> We use ntbackup to create a backup on the "backuserver".

 

Gotcha.

> The server is server 2003, the backupserver is linux.

 

> A kix script makes the drivemapping to right "backupserver"

> Here it goes wrong, after a while it cannot connect anymore to the

> \\servername\sharename, while \\IP-adres\sharename still works.

> After rebooting the server it will work again, but after a period of

> time the problem occurs again.

>

> Microsoft Windows [Version 5.2.3790]

> © Copyright 1985-2003 Microsoft Corp.

>

> C:\Documents and Settings\Administrator.PCWNLRICTPROE>ipconfig /all

>

> Windows IP Configuration

>

> Host Name . . . . . . . . . . . . : PCWNLRICTPROE

> Primary Dns Suffix . . . . . . . : wnl.villeroy-boch.net

> Node Type . . . . . . . . . . . . : Hybrid

> IP Routing Enabled. . . . . . . . : No

> WINS Proxy Enabled. . . . . . . . : No

> DNS Suffix Search List. . . . . . : wnl.villeroy-boch.net

> ads.villeroy-boch.net

> met.villeroy-boch.net

> villeroy-boch.com

>

> Ethernet adapter Local Area Connection:

>

> Connection-specific DNS Suffix . :

> Description . . . . . . . . . . . : Intel® PRO/1000 MT Network

> Connection Physical Address. . . . . . . . . : 00-C0-9F-31-85-86

> DHCP Enabled. . . . . . . . . . . : No

> IP Address. . . . . . . . . . . . : 92.0.0.7

> Subnet Mask . . . . . . . . . . . : 255.255.0.0

> Default Gateway . . . . . . . . . : 92.0.0.254

> DNS Servers . . . . . . . . . . . : 127.0.0.1

> 92.0.0.26

> 192.168.166.16

 

 

I see a few things strange/wrong here....

 

1. Why so many DNS suffixes?

 

2. Why are you using public IP addresses on your LAN? This is not a good

thing...you should be using non-routable IPs.

 

3. Your DNS is not correct - in AD, everything must point *only* to your

internal DNS server's IP address (the LAN IP - don't use the localhost

address) and no others, whether public or private. Your Linux server should

be configured to point only to the internal DNS server IP as well, and also

have wnl.villeroy-boch.net as its primary DNS suffix.

 

 

It looks like