or a server residing in another domain that you don't have any trusts in place with.
-----Original Message----- From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] Sent: Wed, January 08, 2003 2:50 PM To: NT 2000 Discussions Subject: RE: Name resolution quiz Exactly Static entries are really only need for something like a UNIX server running CIFS/samba and can't perform a WINS registration Or maybe an old Mac server that doesn't register with WINS -------------------------------- Rob Weatherly -------------------------------- -----Original Message----- From: Barr, Christopher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:49 PM To: NT 2000 Discussions Subject: RE: Name resolution quiz Rob is 100% correct on this one... Sounds like somebody should be re-reading the entire Chapter 7... Why OH Why would you really need to add static entries, or are you just trying to create more work for yourself. -----Original Message----- From: Weatherly, Rob [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 1:42 PM To: NT 2000 Discussions Subject: RE: Name resolution quiz Please review the below quote from the site you posted: If you read number 1 you will see that a WINS client attempts to refresh its lease 1/2 way through the total lease time, and if the request fails it will try again every 10 minutes. So if a WINS client does this automatically what is the need for a static entry? It does not say that this process is only done during a boot-up or that it is not done on clients that have static IP's. The one thing that is worth noting is that even if it is a Win2k server you should still specify a primary and secondary WINS server in the network properties. And the other thing is that the WINS server it self should always have its OWN IP as its primary and secondary WINS server. When a WINS client refreshes its name, it performs the following steps: 1.) When a client has consumed � of its renewal interval, it sends a name refresh request to the primary WINS server. 2.) If its name is not refreshed by the primary WINS server, the WINS client tries to refresh again in 10 minutes and continues to try the primary WINS server repeatedly every 10 minutes for a total of 1 hour. 3.) The WINS client, after trying to refresh its name registration with the primary WINS server for one hour, stops trying and attempts to refresh its name with the secondary WINS server. 4.) If it is not refreshed by the secondary WINS server, the WINS client tries to refresh its name again using the secondary WINS server in 10 minutes and continues to try every 10 minutes for a total of 1 hour. 5.) The WINS client after trying to refresh on the secondary WINS server for one hour, stops trying and tries to refresh using the primary WINS server. 6.) This process of trying the primary WINS server and then the secondary WINS server continues until the renewal interval is consumed or the WINS client has its name refreshed. 7.) If the WINS client succeeds in refreshing its name, the renewal interval is reset on the WINS server. 8.) If the WINS client fails to register during the renewal interval on either the primary or secondary WINS server the name is released. -------------------------------- Rob Weatherly -------------------------------- -----Original Message----- From: Ken Coughlin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:25 PM To: NT 2000 Discussions Subject: RE: Name resolution quiz I beg to differ. WINS entries are LEASED and must be Released and Refreshed every few days or else the Lease expires. This is from http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn ol/windows2000serv/reskit/tcpip/part2/tcpch07.asp WINS clients must renew their name registrations before the renewal interval expires. The renewal interval determines how long the server stores the name registration as an active record in the WINS database. When a WINS client renews its name registration, it sends a name refresh request to the WINS server. The name refresh request includes the IP address and the NetBIOS name that the client seeks to refresh. The WINS server responds to the name refresh request with a name refresh response that includes a new renewal interval for the name. -----Original Message----- From: Roger Seielstad [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 2:05 PM To: NT 2000 Discussions Subject: RE: Name resolution quiz I'll call BS on that one. Any machine capable of registering itself in WINS (i.e. every Windows based machine) should NEVER, EVER, EVER IN A MILLION YEARS have a static WINS entry. Sounds like your WINS server is configured incorrectly. I've got plenty of NT and Win2k machines that have been up over 180 days without falling out of WINS. Ever. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Ken Coughlin [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 08, 2003 1:55 PM > To: NT 2000 Discussions > Subject: RE: Name resolution quiz > > > You should have a static entry for Servers and other systems > which have a > static IP and don't get rebooted frequently. The alternative > is to run > "nbtstat -RR" every few days, otherwise the WINS server > releases the entry. > > Ken > > -----Original Message----- > From: Andrew S. Baker [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 08, 2003 1:50 PM > To: NT 2000 Discussions > Subject: RE: Name resolution quiz > > > You should not have to add static entries for Windows systems. > > How are your WINS servers configured and how many do you have? > > > > ASB > http://www.ultratech-llc.com/KB > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Lum, David > Sent: Wednesday, January 08, 2003 1:40 PM > To: NT 2000 Discussions > Subject: Name resolution quiz > > > Time to show more of my ignorance. > > PROBLEM: > a) DOMAIN1 DC gets event ID 5719 "No NT domain controller is available > for domain DOMAIN2..." > > b) Using Server Manager to look at DOMAIN2 tells me I get read only > because it can't find the PDC of DOMAIN2 > > TROUBLESHOOTING STEPS: > Attempt to ping Server1 by name: > Unknown Host > > Ping server by IP: > successful replies > > Fine, it can't resolve the name but out of curiosity I try: > > NBTSTAT -a Server1 IP and I get: > Server1 <00> UNIQUE Registered > Server1 <20> UNIQUE Registered > DOMAIN2 <00> GROUP Registered > DOMAIN2 <1C> GROUP Registered > DOMAIN2 <1E> GROUP Registered > Server1 <03> UNIQUE Registered > ADMINISTRATOR <03> UNIQUE Conflict > DOMAIN2 <1B> UNIQUE Registered > DOMAIN2 <1D> UNIQUE Registered > __MSBROWSE__.<01> GROUP Registered > > FIX: DOMAIN1 DC is WINS server, so I added static WINS mapping. Server > manager is now happy and I can ping by name. > > Question: > NBTSTAT uses NetBIOS to resolve the name, so why can't the machine use > the Server1 name to contact it without a WINS (or probably DNS would > work too) entry even with NetBIOS over TCP/IP enabled? > > Dave. > PS this list makes me better troubleshooter, as to collect > all relevant > information sometimes I find the solution before finished the e-mail! > > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
