<div>
You could write a batch file for the users and put it on the desktop as a short term solution. 
 
Back to the problem in hand, when a client fails, before carrying out the /renew and /registerdns, are you able to ping the domain by name? 
 
-BBRazz
</div>

<div>
 
When the issue occurs it needs to be split into a number of possible problems. 
 
Given the fix it's fairly unlikely that DNS is broken, so it would seem appropriate to check the network level first. 
 
So during a failure, can they ping the server? Can they resolve names using nslookup? 
 
Chris 

</div>

<div>
nslookup works, ping to the dns server works, ping to dev.domain.com does not work, ping to the ipadress does work.
</div>

<div>
 
Ping to the Default Gateway? 
 
And Tracert past the default Gateway (e.g. tracert <a href="http://www.google.com)?" rel="ugc">www.google.com)?</a> 
 
Chris 

</div>

<div>
That all works fine, 
 
Its more like 
 
[INTERNET] 
[GATEWAY] 
[OUR MAIN SERVER + DNS] &nbsp;=&gt; [OUR DEVELOPMENT SERVER] 
[CLIENT PC'S] 
 
 
Internet always works fine, never any problems. 
all dev.domain.com's are registered in our DNS server. 
someone goes to dev.domain1.com and it works fine 
couple of hours later it suddenly stops working eventough they just accessed it. 
yet if they try about 5 seconds later dev.domain2.com it works, but domain1 still does not work. 
then only a ipconfig /registerdns or ipconfig /renew fixes this (browser cache?!?). an ipconfig /flushdns does nothing. 
 
 
 
btw the batch file @ their desktop won't work, since they are not allowed to do ipconfig /renew, and i don't know how to allow it to them, now an administrator comes by to execute it as administrator.
</div>

<div>
nslookup does, 
ping does not resolve the name to an ip. 
 
no, we only have our primary dns server configured. (since we don't have any others)
</div>

<div>
 
Interesting. Ping uses the DNS Client to get it's names whereas nslookup makes a request directly against the server. 
 
I take it you've tried updating Network drivers and such? 
 
Again when it's failing can yo run: 
 
ipconfig /displaydns 
 
That shows you the contents of the DNS Cache. I'm wondering if somehow the clients have a &quot;Name does not exist&quot; for the system you're trying to reach. If it does that's a negative cache entry, it should only stay for a maximum of 5 minutes. 
 
Chris 

</div>

<div>
Ok the error occured again.. 
 
results: 
 
ipconfig /displaydns 
dev.123tijdschrift.nl 
------------------------------------------- 
Naam bestaat niet. 
&nbsp; 
 
dev.123tijdschrift.n 
------------------------------------------- 
Naam bestaat niet. 
 
Translated: 
Name does not exist) 
 
somehow it also adds the .n and not just the .nl. 
 
 
 
After a flushdns, which miracously worked this time?!? 
 
 
dev.123tijdschrift.nl 
&nbsp;---------------------------------------- 
Recordnaam . . . . . : dev.123tijdschrift.nl.DaisyconBV.local 
Recordtype . . . . . : 1 
Time-to-Live . . . . : 3590 
Gegevenslengte . . . : 4 
Sectie . . . . . . . : antwoord 
A-record (host). . . : 192.168.1.7 
 
 
Translated: 
 
dev.123tijdschrift.nl 
&nbsp;---------------------------------------- 
Recordname . . . . . : dev.123tijdschrift.nl.DaisyconBV.local 
Recordtype . . . . . : 1 
Time-to-Live . . . . : 3590 
Datalength . . . : 4 
Section . . . . . . . : answer 
A-record (host). . . : 192.168.1.7 

</div>

<div>
Ah second user also had it at the same time, 
for him the flushdns did not work, 
 
he would get the name does not exist 
then the flush dns removed it 
and a new ping or opening of the domain just added it again 
ipconfig /renew fixed it.
</div>

<div>
 
Okay this is odd. 
 
When they try to find the name what are they putting in? Is it for name only? Or for the full FQDN? 
 
And they really don't have any DNS server but the DC? 
 
Chris 

</div>

<div>
Aaaah, Think i've found something... 
 
My collegue disabled the second DNS server, because we used to have these issues. 
Now i've been digging because of your questions and indeed the strange responses, 
and he only turned it of for specific users! 
 
while other users are now having the problems. 
I've completely disabled the second DNS server (Which was an online one which indeed does not know our internal records) 
 
The only thing i'm worried about now, is that if users got moved to the second DNS server, because the first one ap. &quot;couldn't handle it&quot;. What will happen now that we only have 1?
</div>

<div>
 
It'll try harder with the first. 
 
It's odd, but it only does a very basic surface level check to figure out if the server is busy. If there's only one server it won't fail-over to the second, it'll be a bit more patient. 
 
Chris 

</div>

<div>
<div class="content wysiwyg-content">
Our SBS 2003 Server is currently having &quot;hickups&quot; in the DNS server, well its eather that our its some of our workstations. 
 
What happens is we got a lot of &quot;internal&quot; domains, which will be requested from our DNS server. 
Then all of a sudden, it says page not found, and it takes an ipconifg /renew or an ipconfig /registerdns 
to fix t his issue before the page loads. 
 
It used to happen only to 1 user like once a week, but now it seems to be hapenning more often, and to more users. 
 
We're in an 1 server SBS 2003 environment with about 40 - 45 client computers (Windows xp pro). using Symantec anti-virus. 
The browser does not have an effect, wether they use IE 6, 7 or 8, or mozilla firefox 2, 3 it still happens. 
 
Anyone knows where this could come from? 
And any solutions? 
Also does anyone know how to allow users to refresh their IP themselves? so that we have a temporary &quot;quick fix&quot; 
 
Thnx 

</div>
</div>

Our SBS 2003 Server is currently having "hickups" in the DNS server, well its eather that our its some of our workstations.

What happens is we got a lot of "internal" domains, which will be requested from our DNS server.
Then all of a sudden, it says page not found, and it takes an ipconifg /renew or an ipconfig /registerdns
to fix t his issue before the page loads.

It used to happen only to 1 user like once a week, but now it seems to be hapenning more often, and to more users.

We're in an 1 server SBS 2003 environment with about 40 - 45 client computers (Windows xp pro). using Symantec anti-virus.
The browser does not have an effect, wether they use IE 6, 7 or 8, or mozilla firefox 2, 3 it still happens.

Anyone knows where this could come from?
And any solutions?
Also does anyone know how to allow users to refresh their IP themselves? so that we have a temporary "quick fix"

Thnx


SBS 2003 DNS hickups - Users loose connection for a short second

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Microsoft Windows XP is the sixth release of the NT series of operating systems, and was the first to be marketed in a variety of editions: XP Home and XP Professional, designed for business and power users. The advanced features in XP Professional are generally disabled in Home Edition, but are there and can be activated. There were two 64-bit editions, an embedded edition and a tablet edition.