FQDN Does not appear for W2K Exchange on NT4 Exchange server when short NetBIOS name is Pinged

  • Thread starter Thread starter Bill Tomlinson
  • Start date Start date
B

Bill Tomlinson

In the Microsoft KB316886 "HOW TO: Migrate from Exchange Server 5.5 to
Exchange 2000 Server" it requires that you "ping" the short NetBIOS name of
your W2K Exchange server from your NT4 Excahnge server.

The expected result is:
ping 2k-exch-test
pinging 2k-exch-test.someinternaldomain.externaldomain.com [192.168.1.10]
with 32 bytes of data

The results I get are:
ping 2k-exch-test
pinging 2k-exch-test [192.168.1.10] with 32 bytes of data

The article says: "If the FQDN does not appear, configure the proper name
resolution for the Exchange Server 5.5 computer."

My NT4 Exchange server ipconfig information confirms that I am pointing the
DNS to my Windows 2k server which has the Operations Master Domain
Controller role, running DNS and Active Directory.

I have checked that the TCP/IP protocol properties advanced dns settings on
the 2k-exch-test server have the: "Append primary and connection specific
DNS suffixes" radio button selected, and the: "Append parent suffixes of the
primary DNS suffix" box checked, and that the" Register this connectioin's
addresses in DNS" is also checked. I also ran the ipconfig /flushdns and
ipconfig /registerdns commands from the 2k-exch-test server to make sure the
records are current.

I still can not get the FQDN to show up on the NT4 server.

If I ping any short name of any W2K workstation or W2K server from the
2k-exch-test server, w2k-client, or 2k-domain-controller, it retuns the
FQDN. If I ping any short name of any NT4 workstation or NT4 server from
the 2k-exch-test server, w2k-client, or 2k-domain-controller, it only
returns the shortname.

Any help on getting the FQDN to show up on the NT4 Exch server would be
appreciated.
 
In
Bill Tomlinson said:
In the Microsoft KB316886 "HOW TO: Migrate from Exchange Server 5.5 to
Exchange 2000 Server" it requires that you "ping" the short NetBIOS
name of your W2K Exchange server from your NT4 Excahnge server.

The expected result is:
ping 2k-exch-test
pinging 2k-exch-test.someinternaldomain.externaldomain.com
[192.168.1.10] with 32 bytes of data

The results I get are:
ping 2k-exch-test
pinging 2k-exch-test [192.168.1.10] with 32 bytes of data

The article says: "If the FQDN does not appear, configure the proper
name resolution for the Exchange Server 5.5 computer."

My NT4 Exchange server ipconfig information confirms that I am
pointing the DNS to my Windows 2k server which has the Operations
Master Domain Controller role, running DNS and Active Directory.

I have checked that the TCP/IP protocol properties advanced dns
settings on the 2k-exch-test server have the: "Append primary and
connection specific DNS suffixes" radio button selected, and the:
"Append parent suffixes of the primary DNS suffix" box checked, and
that the" Register this connectioin's addresses in DNS" is also
checked. I also ran the ipconfig /flushdns and ipconfig /registerdns
commands from the 2k-exch-test server to make sure the records are
current.

I still can not get the FQDN to show up on the NT4 server.

If I ping any short name of any W2K workstation or W2K server from the
2k-exch-test server, w2k-client, or 2k-domain-controller, it retuns
the FQDN. If I ping any short name of any NT4 workstation or NT4
server from the 2k-exch-test server, w2k-client, or
2k-domain-controller, it only returns the shortname.

Any help on getting the FQDN to show up on the NT4 Exch server would
be appreciated.
Click to expand...

In the NT4's TCP/IP properties, did you configure your domain suffix under
the DNS tab, domain name box?


--
Regards,
Ace

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

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

I did not have this set correctly. When I put the same domain suffix as my
Windows 2K servers it works. I am still a bit confused by this.

My test W2k domain is: roycetest.royceinstruments.com

My NT4 servers domains were set to: royceinstruments.com

When I reset the NT4 server's domains to: roycetest.royceinstruments.com,
the ping command responded with the FQDN that I am looking for. My
confusion is why my NT4 servers need to be in the same domain as the W2k
servers for this to work. Can you provide a bit more wisdom here for me?

Thanks

Bill T.
"Ace Fekay [MVP]"
In
Bill Tomlinson said:
In the Microsoft KB316886 "HOW TO: Migrate from Exchange Server 5.5 to
Exchange 2000 Server" it requires that you "ping" the short NetBIOS
name of your W2K Exchange server from your NT4 Excahnge server.

The expected result is:
ping 2k-exch-test
pinging 2k-exch-test.someinternaldomain.externaldomain.com
[192.168.1.10] with 32 bytes of data

The results I get are:
ping 2k-exch-test
pinging 2k-exch-test [192.168.1.10] with 32 bytes of data

The article says: "If the FQDN does not appear, configure the proper
name resolution for the Exchange Server 5.5 computer."

My NT4 Exchange server ipconfig information confirms that I am
pointing the DNS to my Windows 2k server which has the Operations
Master Domain Controller role, running DNS and Active Directory.

I have checked that the TCP/IP protocol properties advanced dns
settings on the 2k-exch-test server have the: "Append primary and
connection specific DNS suffixes" radio button selected, and the:
"Append parent suffixes of the primary DNS suffix" box checked, and
that the" Register this connectioin's addresses in DNS" is also
checked. I also ran the ipconfig /flushdns and ipconfig /registerdns
commands from the 2k-exch-test server to make sure the records are
current.

I still can not get the FQDN to show up on the NT4 server.

If I ping any short name of any W2K workstation or W2K server from the
2k-exch-test server, w2k-client, or 2k-domain-controller, it retuns
the FQDN. If I ping any short name of any NT4 workstation or NT4
server from the 2k-exch-test server, w2k-client, or
2k-domain-controller, it only returns the shortname.

Any help on getting the FQDN to show up on the NT4 Exch server would
be appreciated.
Click to expand...

In the NT4's TCP/IP properties, did you configure your domain suffix under
the DNS tab, domain name box?


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
 
I think you mis-read Ace's response. The problem is with the "DNS Suffix" of
you NT4 Computer (this is in the TCP/IP -> DNS tab). This is not really a
problem with your NT4's Domain name.

What the suffix does in this instance is to tell your client (the NT4)
something like this: "When I ask you for Bill's infomation, and you look in
your Rolodex, always assume that I am asking you to look for Bill
Tomlinson". If you have multiple sufffixes specified, then the instruction
changes a bit slightly like so "If you can't find Bill Tomlinson, then try
Bill Thomas, Bill Fekay, Bill Akomolafe. Don't give up until you've tried
all of those permutations"

Now, in your original problem, there was no suffix, so the NT4 probably used
WINS broadcast to get the IP of 2k-exch-test and returned that to you.

HTH

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
Bill Tomlinson said:
Ace,

I did not have this set correctly. When I put the same domain suffix as my
Windows 2K servers it works. I am still a bit confused by this.

My test W2k domain is: roycetest.royceinstruments.com

My NT4 servers domains were set to: royceinstruments.com

When I reset the NT4 server's domains to: roycetest.royceinstruments.com,
the ping command responded with the FQDN that I am looking for. My
confusion is why my NT4 servers need to be in the same domain as the W2k
servers for this to work. Can you provide a bit more wisdom here for me?

Thanks

Bill T.
"Ace Fekay [MVP]"
In
Bill Tomlinson said:
In the Microsoft KB316886 "HOW TO: Migrate from Exchange Server 5.5 to
Exchange 2000 Server" it requires that you "ping" the short NetBIOS
name of your W2K Exchange server from your NT4 Excahnge server.

The expected result is:
ping 2k-exch-test
pinging 2k-exch-test.someinternaldomain.externaldomain.com
[192.168.1.10] with 32 bytes of data

The results I get are:
ping 2k-exch-test
pinging 2k-exch-test [192.168.1.10] with 32 bytes of data

The article says: "If the FQDN does not appear, configure the proper
name resolution for the Exchange Server 5.5 computer."

My NT4 Exchange server ipconfig information confirms that I am
pointing the DNS to my Windows 2k server which has the Operations
Master Domain Controller role, running DNS and Active Directory.

I have checked that the TCP/IP protocol properties advanced dns
settings on the 2k-exch-test server have the: "Append primary and
connection specific DNS suffixes" radio button selected, and the:
"Append parent suffixes of the primary DNS suffix" box checked, and
that the" Register this connectioin's addresses in DNS" is also
checked. I also ran the ipconfig /flushdns and ipconfig /registerdns
commands from the 2k-exch-test server to make sure the records are
current.

I still can not get the FQDN to show up on the NT4 server.

If I ping any short name of any W2K workstation or W2K server from the
2k-exch-test server, w2k-client, or 2k-domain-controller, it retuns
the FQDN. If I ping any short name of any NT4 workstation or NT4
server from the 2k-exch-test server, w2k-client, or
2k-domain-controller, it only returns the shortname.

Any help on getting the FQDN to show up on the NT4 Exch server would
be appreciated.
Click to expand...

In the NT4's TCP/IP properties, did you configure your domain suffix under
the DNS tab, domain name box?


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
Click to expand...
 
Nicely put!
:-)

--
Regards,
Ace

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

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

Deji Akomolafe said:
I think you mis-read Ace's response. The problem is with the "DNS Suffix" of
you NT4 Computer (this is in the TCP/IP -> DNS tab). This is not really a
problem with your NT4's Domain name.

What the suffix does in this instance is to tell your client (the NT4)
something like this: "When I ask you for Bill's infomation, and you look in
your Rolodex, always assume that I am asking you to look for Bill
Tomlinson". If you have multiple sufffixes specified, then the instruction
changes a bit slightly like so "If you can't find Bill Tomlinson, then try
Bill Thomas, Bill Fekay, Bill Akomolafe. Don't give up until you've tried
all of those permutations"

Now, in your original problem, there was no suffix, so the NT4 probably used
WINS broadcast to get the IP of 2k-exch-test and returned that to you.

HTH

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
Bill Tomlinson said:
Ace,

I did not have this set correctly. When I put the same domain suffix as my
Windows 2K servers it works. I am still a bit confused by this.

My test W2k domain is: roycetest.royceinstruments.com

My NT4 servers domains were set to: royceinstruments.com

When I reset the NT4 server's domains to: roycetest.royceinstruments.com,
the ping command responded with the FQDN that I am looking for. My
confusion is why my NT4 servers need to be in the same domain as the W2k
servers for this to work. Can you provide a bit more wisdom here for me?

Thanks

Bill T.
"Ace Fekay [MVP]"
In Bill Tomlinson <[email protected]> posted their thoughts, then I offered mine
In the Microsoft KB316886 "HOW TO: Migrate from Exchange Server 5.5 to
Exchange 2000 Server" it requires that you "ping" the short NetBIOS
name of your W2K Exchange server from your NT4 Excahnge server.

The expected result is:
ping 2k-exch-test
pinging 2k-exch-test.someinternaldomain.externaldomain.com
[192.168.1.10] with 32 bytes of data

The results I get are:
ping 2k-exch-test
pinging 2k-exch-test [192.168.1.10] with 32 bytes of data

The article says: "If the FQDN does not appear, configure the proper
name resolution for the Exchange Server 5.5 computer."

My NT4 Exchange server ipconfig information confirms that I am
pointing the DNS to my Windows 2k server which has the Operations
Master Domain Controller role, running DNS and Active Directory.

I have checked that the TCP/IP protocol properties advanced dns
settings on the 2k-exch-test server have the: "Append primary and
connection specific DNS suffixes" radio button selected, and the:
"Append parent suffixes of the primary DNS suffix" box checked, and
that the" Register this connectioin's addresses in DNS" is also
checked. I also ran the ipconfig /flushdns and ipconfig /registerdns
commands from the 2k-exch-test server to make sure the records are
current.

I still can not get the FQDN to show up on the NT4 server.

If I ping any short name of any W2K workstation or W2K server from the
2k-exch-test server, w2k-client, or 2k-domain-controller, it retuns
the FQDN. If I ping any short name of any NT4 workstation or NT4
server from the 2k-exch-test server, w2k-client, or
2k-domain-controller, it only returns the shortname.

Any help on getting the FQDN to show up on the NT4 Exch server would
be appreciated.

In the NT4's TCP/IP properties, did you configure your domain suffix under
the DNS tab, domain name box?


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
Click to expand...
Click to expand...
 
Back
Top