Windows Server 2003 does not open its own share

[Guest amzd]

Hello,

I observed a funny thing. We have several Windows Server 2003/Terminal

Server 2003. They

are part of a domain, let us call it .pac.

Let us call one server Munich.

The servers have several shares, let us call one share on Munich

"Inside".

On server munich I open The Run-Window (Start, run) and then typ in:

\\munich.pac\Inside

The Server does not open the share, it asks for authentication which

never works.

I alway receive:

Logon unsuccessful. Windows is unable to log you on. Be sure that

your

user name and password are correct.

If I type in:

\\munich\Inside

then it opens the share immediately without any question.

If I go to another windows server 2003 or my XP-Client and try

\\munich.pac\Inside

then this works too.

The behaviour is the same on a second Windows 2003 Server.

The servers do not offer their own shares - and only their own shares

- as long as the server name is specified with the domain suffix.

Does anyone have an idea?

This has nothing to do with the TCP/IP-Settings in the network

connections explorer window.

I added the domain suffix and deleted it in the DNS window without

any

changes.

It is not as trivial as it seems. Perhaps s.o. from Microsoft should

look at this.

 

Thank you

Andreas

[Guest Jeff Pitsch]

Re: Windows Server 2003 does not open its own share

 

Perhaps your DNS is not setup correctly. Can you ping the FQDN?

 

On a side note, this is for terminal services and your problem is related to

straight up server functionality. I think you'd have better luck with the

other newsgroups than TS.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"amzd" <Andreas.meyer@dmc-group.de> wrote in message

news:310ffd2c-f666-42eb-a3f0-6117f40ba8ca@j22g2000hsf.googlegroups.com...

> Hello,

> I observed a funny thing. We have several Windows Server 2003/Terminal

> Server 2003. They

> are part of a domain, let us call it .pac.

> Let us call one server Munich.

> The servers have several shares, let us call one share on Munich

> "Inside".

> On server munich I open The Run-Window (Start, run) and then typ in:

> \\munich.pac\Inside

> The Server does not open the share, it asks for authentication which

> never works.

> I alway receive:

> Logon unsuccessful. Windows is unable to log you on. Be sure that

> your

> user name and password are correct.

> If I type in:

> \\munich\Inside

> then it opens the share immediately without any question.

> If I go to another windows server 2003 or my XP-Client and try

> \\munich.pac\Inside

> then this works too.

> The behaviour is the same on a second Windows 2003 Server.

> The servers do not offer their own shares - and only their own shares

> - as long as the server name is specified with the domain suffix.

> Does anyone have an idea?

> This has nothing to do with the TCP/IP-Settings in the network

> connections explorer window.

> I added the domain suffix and deleted it in the DNS window without

> any

> changes.

> It is not as trivial as it seems. Perhaps s.o. from Microsoft should

> look at this.

>

> Thank you

> Andreas