| Author |
Message |
Terry
Guest
|
 Posted:
Tue Nov 08, 2005 1:50 pm Post subject:
DNS Error 6702 |
|
|
I have a Win2K3 server with some DNS issues, checking the DNS log I find it
full of 6702's! DNS of course is stopped.
There are various issues with regards to the Win2K machines not
authenticating on user logon, not finding printer shares etc.
What would I need to do to fix up the DNS config on this server please?
regards
Terry
The network topolgy is:
Zyxel Router at 192.168.1.1 acting as DHCP server
Server at 192.168.1.33 as the only PDC
XPpro client at 192.168.1.235
Two Win2K at 192.168.1.34 & .35
IP Config gives:
Host name ....floyd_svr
Primary DNS suffix...floydmatcham
Node type.... unknown
IP Routing enabled....No
WINS Proxy enabled....No
DNS Suffix search list.... floydmatcham
DHCP enabled.....No
IP address....192.168.1.33
Subnet mask.....255.255.255.0
Default gateway.....192.168.1.1
DNS Servers.....127.0.0.1
195.8.0.33
195.80.0.226
Route Print gives:
Destination Netmask Gateway
Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1
192.168.1.33 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.33 192.168.1.33
20
192.168.1.33 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.1.255 255.255.255.255 192.168.1.33 192.168.1.33 20
224.0.0.0 240.0.0.0 192.168.1.33
192.168.1.33 20
255.255.255.255 255.255.255.255 192.168.1.33 192.168.1.33 1
Default gateway: 192.168.1.1 |
|
| Back to top |
|
 |
Ace Fekay [MVP]
Guest
|
| Posted:
Wed Nov 09, 2005 1:50 am Post subject:
Re: DNS Error 6702 |
|
|
In news:u3jsRHG5FHA.1028@TK2MSFTNGP11.phx.gbl,
Terry <it@REMOVETHISfloydautomatic.co.uk> made this post, which I then
commented about below:
| Quote: | I have a Win2K3 server with some DNS issues, checking the DNS log I
find it full of 6702's! DNS of course is stopped.
There are various issues with regards to the Win2K machines not
authenticating on user logon, not finding printer shares etc.
What would I need to do to fix up the DNS config on this server
please?
regards
Terry
The network topolgy is:
Zyxel Router at 192.168.1.1 acting as DHCP server
Server at 192.168.1.33 as the only PDC
XPpro client at 192.168.1.235
Two Win2K at 192.168.1.34 & .35
IP Config gives:
Host name ....floyd_svr
Primary DNS suffix...floydmatcham
Node type.... unknown
IP Routing enabled....No
WINS Proxy enabled....No
DNS Suffix search list.... floydmatcham
DHCP enabled.....No
IP address....192.168.1.33
Subnet mask.....255.255.255.0
Default gateway.....192.168.1.1
DNS Servers.....127.0.0.1
195.8.0.33
195.80.0.226
Route Print gives:
Destination Netmask Gateway
Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1
192.168.1.33 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.33 192.168.1.33
20
192.168.1.33 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.33 192.168.1.33 20
224.0.0.0 240.0.0.0 192.168.1.33
192.168.1.33 20
255.255.255.255 255.255.255.255 192.168.1.33 192.168.1.33 1
Default gateway: 192.168.1.1
|
Your main issue is your AD DNS domain name (FQDN) is a single label name.
Not
good at all. Why did this occur? Possibly not realizing the way names should
be created prior to implementing the domain, especially during the design
phase. Numerous issues can and will occur due to single label AD DNS domain
names.
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003
Domain (or any AD upgrade or installation):
http://support.microsoft.com/default.aspx?scid=kb;en-us;555040
Another issue is you are using your ISP's DNS for you client machines and
not YOUR internal DNS server.
Also, one more factor is the router is the DHCP server. That guy doesn't
work with DNS Dynamic Updates. Use Windows DHCP.
Recommendations to clean up some of the errors:
1. Remove the 127.0.0.1, 195.8.0.33 and 195.80.0.226 addresses from all the
machines and only use 192.168.1.33 on all machines.
2. In DNS configure a forwarder to go to 195.8.0.33 and 195.80.0.226 .
3. Read this about single lable names:
Single-Label DNS Names:
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
================================= |
|
| Back to top |
|
|
Terry
Guest
|
| Posted:
Wed Nov 09, 2005 1:50 pm Post subject:
Re: DNS Error 6702 |
|
|
Hi Ace,
Thanks for the information. I was aware of the DNS and DHCP not being setup
correctly, but must admit the FQDN issue is of interest.
I was asked to have a look at this server as I had built a hi-spec XPpro
client for the company and during the telecon support I gave to get the new
machine onto the network I determined something quirky was happening. I
managed to get to see the server this week and was amazed that the network
worked at all. I'm guessing that most of the communication between the
machines is only happening because of P2P connectivity.
My experience of a Server 2003 network amounts to just one, but I did go
through Mark Minasi's great book to get it right and did test bench the
server for a month before moving it into production, hence the network at my
workplace functions as per the spec.
The owner of the 'duff' network was provided with a vanilla server box
loaded with an OEM Win2K3 OS. Further, he had asked for the OS/Data
partitions to be mirrored onto another disk, his preferred method of
protecting his data. What he didn't realise was his stuff was mirrored
between two partitions on just one disk! the only one fitted.
I have suggested that another disk be fitted, reload the OS preferably with
a new gold release with SA, fit tape backup and up the memory from 256MB to
at least 1GB leaving the Athlon 1.6GB as is. That will give me an
opportunity to sort his network out with minimum cost.
My wish list would have been a new 'small' server grade machine like the HP
ML series with perhaps a HP Carepack to give some measure of hardware
support.
Needless to say the outfit that supplied and maintained his network are
finally, after months of poor support, well and truly ditched.
Thanks again,
Regards
Terry
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:OwHq0bM5FHA.3276@TK2MSFTNGP10.phx.gbl...
| Quote: | In news:u3jsRHG5FHA.1028@TK2MSFTNGP11.phx.gbl,
Terry <it@REMOVETHISfloydautomatic.co.uk> made this post, which I then
commented about below:
I have a Win2K3 server with some DNS issues, checking the DNS log I
find it full of 6702's! DNS of course is stopped.
There are various issues with regards to the Win2K machines not
authenticating on user logon, not finding printer shares etc.
What would I need to do to fix up the DNS config on this server
please?
regards
Terry
The network topolgy is:
Zyxel Router at 192.168.1.1 acting as DHCP server
Server at 192.168.1.33 as the only PDC
XPpro client at 192.168.1.235
Two Win2K at 192.168.1.34 & .35
IP Config gives:
Host name ....floyd_svr
Primary DNS suffix...floydmatcham
Node type.... unknown
IP Routing enabled....No
WINS Proxy enabled....No
DNS Suffix search list.... floydmatcham
DHCP enabled.....No
IP address....192.168.1.33
Subnet mask.....255.255.255.0
Default gateway.....192.168.1.1
DNS Servers.....127.0.0.1
195.8.0.33
195.80.0.226
Route Print gives:
Destination Netmask Gateway
Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1
192.168.1.33 20
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.33 192.168.1.33
20
192.168.1.33 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.33 192.168.1.33
20 224.0.0.0 240.0.0.0 192.168.1.33
192.168.1.33 20
255.255.255.255 255.255.255.255 192.168.1.33 192.168.1.33 1
Default gateway: 192.168.1.1
Your main issue is your AD DNS domain name (FQDN) is a single label name.
Not
good at all. Why did this occur? Possibly not realizing the way names
should
be created prior to implementing the domain, especially during the design
phase. Numerous issues can and will occur due to single label AD DNS
domain
names.
Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003
Domain (or any AD upgrade or installation):
http://support.microsoft.com/default.aspx?scid=kb;en-us;555040
Another issue is you are using your ISP's DNS for you client machines and
not YOUR internal DNS server.
Also, one more factor is the router is the DHCP server. That guy doesn't
work with DNS Dynamic Updates. Use Windows DHCP.
Recommendations to clean up some of the errors:
1. Remove the 127.0.0.1, 195.8.0.33 and 195.80.0.226 addresses from all
the
machines and only use 192.168.1.33 on all machines.
2. In DNS configure a forwarder to go to 195.8.0.33 and 195.80.0.226 .
3. Read this about single lable names:
Single-Label DNS Names:
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
If this post is viewed at a non-Microsoft community website, and you were
to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public
newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
|
|
|
| Back to top |
|
|
Ace Fekay [MVP]
Guest
|
| Posted:
Thu Nov 10, 2005 1:51 am Post subject:
Re: DNS Error 6702 |
|
|
Terry, respsonses are in-line...
In news:OxKSVgR5FHA.2864@tk2msftngp13.phx.gbl,
Terry <it@REMOVETHISfloydautomatic.co.uk> made this post, which I then
commented about below:
| Quote: | Hi Ace,
Thanks for the information. I was aware of the DNS and DHCP not being
setup correctly, but must admit the FQDN issue is of interest.
|
Also to note of interest is the underscore in the computer name. It's an
illegal DNS character. It may cause additional issues, but the single label
name is a bigger one.
| Quote: |
I was asked to have a look at this server as I had built a hi-spec
XPpro client for the company and during the telecon support I gave to
get the new machine onto the network I determined something quirky
was happening. I managed to get to see the server this week and was
amazed that the network worked at all. I'm guessing that most of the
communication between the machines is only happening because of P2P
connectivity.
|
Possibly working due to NetBIOS connectivity. But I'm suprised that Kerberos
authentication is working without any probs.
| Quote: |
My experience of a Server 2003 network amounts to just one, but I did
go through Mark Minasi's great book to get it right and did test
bench the server for a month before moving it into production, hence
the network at my workplace functions as per the spec.
|
Mark wrote a great book!
| Quote: |
The owner of the 'duff' network was provided with a vanilla server box
loaded with an OEM Win2K3 OS. Further, he had asked for the OS/Data
partitions to be mirrored onto another disk, his preferred method of
protecting his data. What he didn't realise was his stuff was mirrored
between two partitions on just one disk! the only one fitted.
|
Wow, how fortunate the drive didn't fail.
| Quote: |
I have suggested that another disk be fitted, reload the OS
preferably with a new gold release with SA, fit tape backup and up
the memory from 256MB to at least 1GB leaving the Athlon 1.6GB as is.
That will give me an opportunity to sort his network out with minimum
cost.
|
Surprised there's only 256megs in the machine. That's pretty short.
| Quote: |
My wish list would have been a new 'small' server grade machine like
the HP ML series with perhaps a HP Carepack to give some measure of
hardware support.
Needless to say the outfit that supplied and maintained his network
are finally, after months of poor support, well and truly ditched.
Thanks again,
Regards
Terry
|
Good luck Terry! Post back if you have any questions.
Ace |
|
| Back to top |
|
|
Terry
Guest
|
| Posted:
Thu Nov 10, 2005 1:50 pm Post subject:
Re: DNS Error 6702 |
|
|
Hi Ace,
On discussing the next steps to get the server and network fixed I did ask
some questions about how the current server came to be installed. The server
prior to that was a Win2K box, the maintainers at that time claimed the box
was not suitable to run Win2K3 and provided the current box.
I reckon the old Win2K OS and data was ghosted onto the new box and an in
place upgrade to Win2K3 carried out, no surprise there! That would also
explain the non-FQDN and strange drive letters used by the OS, F & G, what a
mess!
Regarding the forwarding configs, is slaving them a good idea?
Regards
Terry
"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:%235qrr5X5FHA.3296@TK2MSFTNGP09.phx.gbl...
| Quote: | Terry, respsonses are in-line...
In news:OxKSVgR5FHA.2864@tk2msftngp13.phx.gbl,
Terry <it@REMOVETHISfloydautomatic.co.uk> made this post, which I then
commented about below:
Hi Ace,
Thanks for the information. I was aware of the DNS and DHCP not being
setup correctly, but must admit the FQDN issue is of interest.
Also to note of interest is the underscore in the computer name. It's an
illegal DNS character. It may cause additional issues, but the single
label name is a bigger one.
I was asked to have a look at this server as I had built a hi-spec
XPpro client for the company and during the telecon support I gave to
get the new machine onto the network I determined something quirky
was happening. I managed to get to see the server this week and was
amazed that the network worked at all. I'm guessing that most of the
communication between the machines is only happening because of P2P
connectivity.
Possibly working due to NetBIOS connectivity. But I'm suprised that
Kerberos authentication is working without any probs.
My experience of a Server 2003 network amounts to just one, but I did
go through Mark Minasi's great book to get it right and did test
bench the server for a month before moving it into production, hence
the network at my workplace functions as per the spec.
Mark wrote a great book!
The owner of the 'duff' network was provided with a vanilla server box
loaded with an OEM Win2K3 OS. Further, he had asked for the OS/Data
partitions to be mirrored onto another disk, his preferred method of
protecting his data. What he didn't realise was his stuff was mirrored
between two partitions on just one disk! the only one fitted.
Wow, how fortunate the drive didn't fail.
I have suggested that another disk be fitted, reload the OS
preferably with a new gold release with SA, fit tape backup and up
the memory from 256MB to at least 1GB leaving the Athlon 1.6GB as is.
That will give me an opportunity to sort his network out with minimum
cost.
Surprised there's only 256megs in the machine. That's pretty short.
My wish list would have been a new 'small' server grade machine like
the HP ML series with perhaps a HP Carepack to give some measure of
hardware support.
Needless to say the outfit that supplied and maintained his network
are finally, after months of poor support, well and truly ditched.
Thanks again,
Regards
Terry
Good luck Terry! Post back if you have any questions.
Ace
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in