Writing to shares on DNS Aliases

[Adrian Marsh (NNTP)]

Hi,

Following on from a post I made in .advanced_server, I'm having
problems writing to an aliased DNS name.

swocmpq01.my.some.domain has a DNS alias of logs.my.some.domain

On client PCs, theres an AT script that runs, and tries to write to
\\logs.my.some.domain\logs$\log.txt. It runs as user System

If I use \\logs... then it fails. I get Access Denied. If I write to
\\swocmpq01.... then it works...

I've applied the registry tweak to allow swocmpq01 to use SMB aliases
(per http://support.microsoft.com/default.aspx?scid=kb;en-us;281308)...
But as this is more to do with DNS than WINS, then I'm assuming theres
something else thats causing it.

Any ideas???

Adrian

 

[Guest]

Here's the instructions on the registry changes you need to make to accept
multiple names:
-- http://www.msresource.net/content/view/16/47/


However there are, apparently, some security concerns with this. I believe
Kerberos doesn't work - your machine will resort to downlevel communication.
But don't have any info. on this point at hand.

However I've used this method many times and have seen no ill effects.

Hope this helps,


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/

 

[Adrian Marsh (NNTP)]

Paul,

Thats the same info as I had before, and that is setup.

I think though that as I'm referencing from 2000/xp clients, and using
the fully qualified DNS name \\logs.my.some.domain instead of \\logs,
then the lanmanserver doesn't come into it (i think) as thats a
WINs/Netbios thing (?)

Indeed if I put \\logs into explorer on a machine in the same network (I
don't have a WINs server), then explorer does find that machine. Without
that reg hack it would reject it. The server \\logs is also a DC if
that makes any difference.

Adrian

 

[ptwilliams]

I'll run some tests tomorrow and get back to you...


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net
______________________________________
Paul,

Thats the same info as I had before, and that is setup.

I think though that as I'm referencing from 2000/xp clients, and using
the fully qualified DNS name \\logs.my.some.domain instead of \\logs,
then the lanmanserver doesn't come into it (i think) as thats a
WINs/Netbios thing (?)

Indeed if I put \\logs into explorer on a machine in the same network (I
don't have a WINs server), then explorer does find that machine. Without
that reg hack it would reject it. The server \\logs is also a DC if
that makes any difference.

Adrian

 

[Adrian Marsh (NNTP)]

Thanks Paul...

 

[admir]

Hi there,

I am working

I have/had the same problem like you. I was able to reach shares on a server
usning alias names but, after removing mcaffee av software and installing
symantec av, alias names stoped working for some reason.

I folowed this instructions: Make note that they are not the same!!!! (you
can do the instructions of both articles and then restart the server)

http://support.microsoft.com/default.aspx?scid=kb;en-us;281308

AND

http://www.msresource.net/content/view/16/47/

After that I was able to reach the server, by using the alias name, from
server it self and some machines on the network. But not all of them.

What I did is: I simply remowed those machines from the domain and added
them again. Evrything works fine now.

I hoope it works for you too.

Regards,

Admir