A
amzd
Guest
Hello,
I observed a funny thing. We have several Windows 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
I observed a funny thing. We have several Windows 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