Server alias.

[Fernando \(CBA\)]

Hi.
We have a windows 2000 server and we want it to have an alias.

I've followed the instructions of http://support.microsoft.com/?id=281308:

-------------------------------------------------------
1. Create the CNAME record for the file server on the appropriate DNS
server, if that the CNAME record is not already present.
2. Apply the hotfix to the computer for which the CNAME record was created,
not the DNS server. (Unless the DNS server and file server in question is
the same computer, and then all of the changes is applied is to that
server.) This hotfix affects the LAN Manager Server Service and does not
affect DNS functionality.
3. Apply the following registry change to the file server to which you
installed the hotfix. To do so:
a) Start Registry Editor (Regedt32.exe).
b) Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c) On the Edit menu, click Add Value, and then add the following registry
value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
d) Quit Registry Editor
-------------------------------------------------------

That let me execute \\aliasname in a windows xp client.
The windows 98 client can ping the alias name but cant execute \\aliasname

I' ve tried to create alias in the WINS server. That let me ping the new
alias name but either windows XP or windows 98 can't execute \\aliasname.

I really need \\aliasname to work on windows 98. Any ideas?
Thanks in advance.

We want to create an alias name because the name of the server is
"serverwk00" but when a win98 client goes to the network neighborhood and
tries to execute a file it says "can't execute \\serverwk\c\example.exe
....." (note that the name should be "serverwk00" not "serverwk")

 

[Ace Fekay [MVP]]

In

Hi.
We have a windows 2000 server and we want it to have an alias.

I've followed the instructions of
http://support.microsoft.com/?id=281308:

-------------------------------------------------------
1. Create the CNAME record for the file server on the appropriate DNS
server, if that the CNAME record is not already present.
2. Apply the hotfix to the computer for which the CNAME record was
created, not the DNS server. (Unless the DNS server and file server
in question is the same computer, and then all of the changes is
applied is to that server.) This hotfix affects the LAN Manager
Server Service and does not affect DNS functionality.
3. Apply the following registry change to the file server to which you
installed the hotfix. To do so:
a) Start Registry Editor (Regedt32.exe).
b) Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
c) On the Edit menu, click Add Value, and then add the following
registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
d) Quit Registry Editor
-------------------------------------------------------

That let me execute \\aliasname in a windows xp client.
The windows 98 client can ping the alias name but cant execute
\\aliasname

I' ve tried to create alias in the WINS server. That let me ping the
new alias name but either windows XP or windows 98 can't execute
\\aliasname.

I really need \\aliasname to work on windows 98. Any ideas?
Thanks in advance.

We want to create an alias name because the name of the server is
"serverwk00" but when a win98 client goes to the network neighborhood
and tries to execute a file it says "can't execute
\\serverwk\c\example.exe ...." (note that the name should be
"serverwk00" not "serverwk")

I think you probably should try using WINS for this functionality. CNAMES
are problematic when it comes to a UNC or Network Neighborhood. They just
don't work. UNCs and Network Neighborhood rely on either NetBIOS (legacy
clients such as NT4, Win9x or WinME) or Direct SMB Host connections (for
W2k, W2k3, or XP). From what I've seen, it will not work with a single CNAME
on a legacy client, since those operating systems treats it as a NetBIOS
name and their resolution method is different then the newer operating
systems because it looks at NetBIOS resolution first.

I believe that you may be able to alter the name resolution method to force
a legacy client to try to resolve thru the HOSTS method (using DNS) first
instead of NetBIOS, which is what you need it to do. See if this article
helps you with this task:

139270 - How to Change Name Resolution Order on Windows 95 and Windows NT:
http://support.microsoft.com/default.aspx?scid=kb;en-us;139270

Here's another article that *may* be of interest, depending on your
scenario.
DNS CNAME Name Resolution Does Not Work if a Record Lives in Delegated
Subzone (248123):
http://support.microsoft.com/?id=248123

If you can't get it to work for your legacy clients, WINS would be your
better answer here.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Fernando \(CBA\)]

I think you probably should try using WINS for this functionality. CNAMES

I've tried do it using WINS. I've added statics entries in the wins server
but this only let me ping the aliasname in the clients, execute \\aliasname
doesn't work either windows XP or windows 98 clients. Should it work?
Have you ever tried it on windows 2000 server?

I believe that you may be able to alter the name resolution method to force
a legacy client to try to resolve thru the HOSTS method (using DNS) first
instead of NetBIOS, which is what you need it to do. See if this article
helps you with this task:

139270 - How to Change Name Resolution Order on Windows 95 and Windows NT:
http://support.microsoft.com/default.aspx?scid=kb;en-us;139270

I can't try this now, i'll do it tomorrow.

Thanks for the help.

 

[Ace Fekay [MVP]]

In

I've tried do it using WINS. I've added statics entries in the wins
server but this only let me ping the aliasname in the clients,
execute \\aliasname doesn't work either windows XP or windows 98
clients. Should it work?
Have you ever tried it on windows 2000 server?

Actually no, I haven't tried this method with any machines. I usually just
go with whatever NetBIOS name the machine has or use the FQDN and instruct
users likewise, unless it's a mapped drive, and just map it for them or use
DFS.

When you say "execute", do you mean you're *just* typing it in (in a
Start/Run command) such as:
\\aliasname
And not really "executing" an executable?

Unless I'm getting confused as to what you mean by "execute". I am just
assuming you are saying that you are simply typing in the UNC into the Run
command line and not really "executing" an executable file.

Either way, \\aliasname should work if using WINS. There may also be an
issue with duplicate NetBIOS names with clients. There's an article
describing this as well.... multiple NetBIOS names can be problematic as
well. It leads to that old TV show reference where the guy introduces
himself as Larry and this is my other brother Larry (or something like
that). I think it was from the Newhart Show? Can't remember.

How can I define multiple NetBIOS names for a machine:
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14475

The additonal [mulitple] NetBIOS name of my server does not work for print
services.:
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14529

I can't try this now, i'll do it tomorrow.

Thanks for the help.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Fernando \(CBA\)]

Actually no, I haven't tried this method with any machines. I usually just
go with whatever NetBIOS name the machine has or use the FQDN and instruct
users likewise, unless it's a mapped drive, and just map it for them or use
DFS.

I'm confused with this statement. If I create an alias with the DNS-CNAME
method:

·Windows XP can execute:
\\aliasname
net view \\aliasname
\\aliasname.cba.local
net view \\aliasname.cba.local

·Windows 98:
ping aliasname -> it says: doing ping to "aliasname.cba.local". It works
OK
\\aliasname -> name not found
net view \\aliasname -> Error 53
\\aliasname.cba.local ->name not found
net view \\realname.cba.local -> it works
net view \\aliasname.cba.local -> syntax error. ?!?!
net use j: \\aliasname.cba.local\c ->IT WORKS. Really surprising to me.

When you say "execute", do you mean you're *just* typing it in (in a
Start/Run command) such as:
\\aliasname
And not really "executing" an executable?

Yes, I mean just typing \\asliasname in the start/run.

Either way, \\aliasname should work if using WINS. There may also be an
issue with duplicate NetBIOS names with clients. There's an article
describing this as well.... multiple NetBIOS names can be problematic as

static entries in the wins server only let me ping the new alias name. No
matter if windowsXP or windows98
Can be a multiple NICs problem related?. The windows 2000 server has 3 NICs

well. It leads to that old TV show reference where the guy introduces
himself as Larry and this is my other brother Larry (or something like
that). I think it was from the Newhart Show? Can't remember.



How can I define multiple NetBIOS names for a machine:
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14475

I tried this method before me first post. It just doesn't work to me . It
doesn't create new wins entries.

This is a piece of a wide spreaded 'article' on the net. windows 98 related:

------------------------------
This section describes variables for subkeys that appear in the
following registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP\
ServiceProvider

The following keys describe the order used to resolve host names. A
lower number sets a higher priority for name resolution. These settings
are used for 16-bit Windows Sockets, which need to rely on the resolvers
that are expected to take the least time. The numbers indicate the
default values specified in Windows.

LocalPriority = 499
HostsPriority = 500
DNSPriority = 2000
NetbtPriority = 2001
------------------------------

I understand:
LocalPriority -> broadcast
HostsPriority -> WINS
DNSPriority -> DNS
NetbtPriority -> LMHOSTS

I've tried the following in a windows 98 client:
·remove all DNS configuration
·remove all WINS configuration
·ping cba9 -> it says 192.168.0.2
·Completely inverse priorities. Edit "lmhosts." with "cba9 192.168.0.200"
·restart ....
·ping cba9 -> it still says 192.168.0.2


It seems that this priorities doesn't work
Do you think is it something about the "These settings
are used for 16-bit Windows Sockets, which need... "?

Quote from my first post:

We want to create an alias name because the name of the
server is "serverwk00" but when a win98 client goes to
the network neighborhood and tries to execute a file it says
"can't execute \\serverwk\c\example.exe ...." (note that
the name should be "serverwk00" not "serverwk")

I tried disabling DNS and WINS configuration on the windows 98 client and
the behaviour was the same.
I can execute \\89.0.0.3\c\example.exe
If I execute: "net use f: 89.0.0.3\shared" in windows 98, "My computer"
shows: "shared on 89.0.0.3 (f".
After that, If I restart the computer and go to "My computer" shows: f:,
"shared on serverwk (f" and the problem is back again.

Why does it associate 89.0.0.3 --> "serverwk"?
I can't try now: "nbtstat -A 89.0.0.3" to see the answer. I'll try on
tuesday.

I'm very frustrated with this problem.
thank you VERY MUCH for your help.

 

[Ace Fekay [MVP]]

In

I'm confused with this statement. If I create an alias with the
DNS-CNAME method:

·Windows XP can execute:
\\aliasname
net view \\aliasname
\\aliasname.cba.local
net view \\aliasname.cba.local

·Windows 98:
ping aliasname -> it says: doing ping to "aliasname.cba.local".
It works OK
\\aliasname -> name not found
net view \\aliasname -> Error 53
\\aliasname.cba.local ->name not found
net view \\realname.cba.local -> it works
net view \\aliasname.cba.local -> syntax error. ?!?!
net use j: \\aliasname.cba.local\c ->IT WORKS. Really surprising
to me.


Yes, I mean just typing \\asliasname in the start/run.


static entries in the wins server only let me ping the new alias
name. No matter if windowsXP or windows98
Can be a multiple NICs problem related?. The windows 2000 server has
3 NICs


I tried this method before me first post. It just doesn't work to me
. It doesn't create new wins entries.


This is a piece of a wide spreaded 'article' on the net. windows 98
related:

------------------------------
This section describes variables for subkeys that appear in the
following registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP\
ServiceProvider

The following keys describe the order used to resolve host names. A
lower number sets a higher priority for name resolution. These
settings
are used for 16-bit Windows Sockets, which need to rely on the
resolvers that are expected to take the least time. The numbers
indicate the
default values specified in Windows.

LocalPriority = 499
HostsPriority = 500
DNSPriority = 2000
NetbtPriority = 2001
------------------------------

I understand:
LocalPriority -> broadcast
HostsPriority -> WINS
DNSPriority -> DNS
NetbtPriority -> LMHOSTS

I've tried the following in a windows 98 client:
·remove all DNS configuration
·remove all WINS configuration
·ping cba9 -> it says 192.168.0.2
·Completely inverse priorities. Edit "lmhosts." with "cba9
192.168.0.200" ·restart ....
·ping cba9 -> it still says 192.168.0.2


It seems that this priorities doesn't work
Do you think is it something about the "These settings
are used for 16-bit Windows Sockets, which need... "?

Quote from my first post:

I tried disabling DNS and WINS configuration on the windows 98 client
and the behaviour was the same.
I can execute \\89.0.0.3\c\example.exe
If I execute: "net use f: 89.0.0.3\shared" in windows 98, "My
computer" shows: "shared on 89.0.0.3 (f".
After that, If I restart the computer and go to "My computer" shows:
f:, "shared on serverwk (f" and the problem is back again.

Why does it associate 89.0.0.3 --> "serverwk"?
I can't try now: "nbtstat -A 89.0.0.3" to see the answer. I'll try on
tuesday.

I'm very frustrated with this problem.
thank you VERY MUCH for your help.

Wow, you do have some headaches about this. Sorry to hear. Yes, to your
question about mutliple NICs, that is very problematic with both NetBIOS and
hosts (DNS) names.

Not sure why on Win98 that it won;'t take the reg change, but maybe it is
due to the 16bit client issue only. Win98, and the same with WinME and NT4
all use NetBIOS as their basis, hence why they try NetBIOS first. Win2k and
newer uses hosts names as their basis, so that's why you're seeing the
different behavior. That's why on XP it will work with using the alias as
part of the UNC. Win98 'thinks' it's a NetBIOS name, hence it will try the
NetBIOS resolution first and fail. But yes, mutliple NICs can be an issue,
especially if 3 on it. One of them becomes the 'default', which would be the
first one in the binding order (Network & Dialup/Adv Menu/Adv Settings). You
can shuffle them around and see what happens.

Sorry I can't think of anything more for you.
:-(

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Sna]

Hi (i'm fernando (CBA))

I found the problem!!!
Every user has on their user-script a line that executes the trend antivirus
autoupdate. This executable seems to be an old ms-dos program for
compatibility and caused all the problems on the system. :S
I replaced in the script the line \\serverwk00\c\autopcc.exe with "net use
k: \\serverwk00\c\" "k:\autopcc" and all the system problems went away.

Thak you very much Ace.