Repost "Trevor Christie" <bbtrev[ at ]gmail.com> 6/25/2007 3:52:19 PM Does anyone have any thoughts on the below? "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> wrote in message news:Oa8csOrsHHA.2124[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > Read inline please. > > In news:hoTdi.32488$kY6.27290[ at ]edtnps82, > Trevor Christie <bbtrev[ at ]gmail.com> typed: >> So Kevin, are you saying that in our domain suffix search list we >> should have: >> >> internal.mycompany.com >> printer.internal.mycompany.com >> net.internal.mycompany.com >> >> In my mind, this would make sense if we were referencing these >> devices by hostname only. However when we reference printers, they >> are referenced by printername.printers. Then when the suffix >> (internal.mycompany.com) is appended, all is well. > > You did not state this in your original post, but I don't think this is a > good idea because these names can only be resolved by DNS, and will not > fail > over to NetBIOS resolution. It is also affected by the search order, and > can > be construed by the DNS client to be a DNS name and could send the name to > DNS without appending a suffix. NetBIOS is junk and we will never count on it. We have removed all but one WINS server and this is due only to Exchange. The reason behind the separation into subdomains is mostly for organization. We have 1800+ records under internal.mycompany.com and it is of value to us to segregate printers and network devices into separate areas. When you say "can be construed by the DNS client to be a DNS name and could send the name to DNS without appending a suffix." I would think that if this were an issue, that we would see the symptoms whether the internet was present or not. >> >> So let me just re-itterate that under normal operation this works >> perfectly well. It was just when we lost internet (and thereby lost >> external DNS) that we lost the ability to reach these devices unless >> explicitly specifying the FQDN. To ping printer1.printers would fail, >> but pinging printer1.printers.internal.mycompany.com worked fine. > > Are you using your internal AD DNS servers only in TCP/IP properties? Yes, the only DNS servers that are listed in any client (DNS client, ie all servers) are internal DNS servers. External DNS is found through the servers listed on the "Root Hints" tab on the properties of the DNS server. >> Also, oddly, an nslookup of printer1.printers successfully resolves. > Nslookup gets it DNS server list and DNS suffix search list from the DNS > client, but bypasses the DNS Client cache. I'm certain that client cache had nothing to do with this as this affected all printers, therefore anything in the client cache would have been correct. >> I have checked a couple of the print servers and NetBIOS over TCP/IP >> is enabled. > This would be basically useless since you do not access the Printers by a > NetBIOS name. > > > -- > Best regards, > Kevin D. Goodknecht Sr. [MVP] > Hope This Helps > > =================================== > When responding to posts, please "Reply to Group" > via your newsreader so that others may learn and > benefit from your issue, to respond directly to > me remove the nospam. from my email address. > =================================== > http://www.lonestaramerica.com/ > http://support.wftx.us/ > http://message.wftx.us/ > =================================== > Use Outlook Express?... Get OE_Quotefix: > It will strip signature out and more > http://home.in.tum.de/~jain/software/oe-quotefix/ > =================================== > Keep a back up of your OE settings and folders > with OEBackup: > http://www.oehelp.com/OEBackup/Default.aspx > =================================== > >

Re: Repost "Ace Fekay [MVP]" <PleaseAskMe[ at ]SomeDomain.com> 6/29/2007 11:02:36 AM In news:TwRfi.10929$xk5.1582[ at ]edtnps82, Trevor Christie <bbtrev[ at ]gmail.com> typed: [Quoted Text] > Does anyone have any thoughts on the below? > > > "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> wrote in > message news:Oa8csOrsHHA.2124[ at ]TK2MSFTNGP02.phx.gbl... >> Read inline please. >> >> In news:hoTdi.32488$kY6.27290[ at ]edtnps82, >> Trevor Christie <bbtrev[ at ]gmail.com> typed: >>> So Kevin, are you saying that in our domain suffix search list we >>> should have: >>> >>> internal.mycompany.com >>> printer.internal.mycompany.com >>> net.internal.mycompany.com >>> >>> In my mind, this would make sense if we were referencing these >>> devices by hostname only. However when we reference printers, they >>> are referenced by printername.printers. Then when the suffix >>> (internal.mycompany.com) is appended, all is well. >> >> You did not state this in your original post, but I don't think this >> is a good idea because these names can only be resolved by DNS, and >> will not fail >> over to NetBIOS resolution. It is also affected by the search order, >> and can >> be construed by the DNS client to be a DNS name and could send the >> name to DNS without appending a suffix. > > NetBIOS is junk and we will never count on it. We have removed all > but one WINS server and this is due only to Exchange. > The reason behind the separation into subdomains is mostly for > organization. We have 1800+ records under internal.mycompany.com and > it is of value to us to segregate printers and network devices into > separate areas. When you say "can be construed by the DNS client to > be a DNS name and could send the name to DNS without appending a > suffix." I would think that if this were an issue, that we would see > the symptoms whether the internet was present or not. >>> >>> So let me just re-itterate that under normal operation this works >>> perfectly well. It was just when we lost internet (and thereby lost >>> external DNS) that we lost the ability to reach these devices unless >>> explicitly specifying the FQDN. To ping printer1.printers would >>> fail, but pinging printer1.printers.internal.mycompany.com worked >>> fine. >> >> Are you using your internal AD DNS servers only in TCP/IP properties? > > Yes, the only DNS servers that are listed in any client (DNS client, > ie all servers) are internal DNS servers. External DNS is found > through the servers listed on the "Root Hints" tab on the properties > of the DNS server. > >>> Also, oddly, an nslookup of printer1.printers successfully resolves. >> Nslookup gets it DNS server list and DNS suffix search list from the >> DNS client, but bypasses the DNS Client cache. > > I'm certain that client cache had nothing to do with this as this > affected all printers, therefore anything in the client cache would > have been correct. > >>> I have checked a couple of the print servers and NetBIOS over TCP/IP >>> is enabled. >> This would be basically useless since you do not access the Printers >> by a NetBIOS name. >> >> >> -- >> Best regards, >> Kevin D. Goodknecht Sr. [MVP] >> Hope This Helps >> >> =================================== >> When responding to posts, please "Reply to Group" >> via your newsreader so that others may learn and >> benefit from your issue, to respond directly to >> me remove the nospam. from my email address. >> =================================== >> http://www.lonestaramerica.com/ >> http://support.wftx.us/ >> http://message.wftx.us/ >> =================================== >> Use Outlook Express?... Get OE_Quotefix: >> It will strip signature out and more >> http://home.in.tum.de/~jain/software/oe-quotefix/ >> =================================== >> Keep a back up of your OE settings and folders >> with OEBackup: >> http://www.oehelp.com/OEBackup/Default.aspx >> =================================== YOu said you disabled NetBIOS due to YOUR opinion it is "junk," correct? Do you have a single label name called "printers" created in DNS? You mentioned you access your printers as printername.printers, hence the question. It also does not make sense that if you lose internet connectivity, that you are unable to resolve your internal printers via FQDN. What may be happening if one thinks this out further, is that your single label name query MUST be sent out to the Root servers for resolution because DNS believes it is a TLD (top level domain name, such as com, net, edu, etc). This was the main reaons Microsoft removed the ability for Windows machines to work properly with single label names. There were numerous complaints from ISC that administrators unknowingly (misguided, uninformed, didn't attend a class, or for whatever reason) were using single label names for their AD domain names (and other names) and non understanding the implications it has on the Internet Root servers. Ace -- Regards, Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP Microsoft MVP - Directory Services Microsoft Certified Trainer Infinite Diversities in Infinite Combinations Having difficulty reading or finding responses to your post? Instead of the website you're using, try using OEx (Outlook Express or any other newsreader), and configure a news account, pointing to news.microsoft.com. Anonymous access. It's free - no username or password required nor do you need a Newsgroup Usenet account with your ISP. It connects directly to the Microsoft Public Newsgroups. OEx allows you o easily find, track threads, cross-post, sort by date, poster's name, watched threads or subject. It's easy: How to Configure OEx for Internet News http://support.microsoft.com/?id=171164 "Quitting smoking is easy. I've done it a thousand times." - Mark Twain