ipconfig /flushdns

[lwardle]

Can anyone get into the nuts and bolts of what this command actually
does - what is causes the workstation to do in a domain environment.
I know it clears out the workstation resolver cache - but I am more
curious as to the impact this has in a redirected folder scenerio

 

[David H. Lipman]

From: <[email protected]>

| Can anyone get into the nuts and bolts of what this command actually
| does - what is causes the workstation to do in a domain environment.
| I know it clears out the workstation resolver cache - but I am more
| curious as to the impact this has in a redirected folder scenerio

It does nothing more than flushes a Domain-Name cache on the PC.

 

[lwardle]

From: <[email protected]>

| Can anyone get into the nuts and bolts of what this command actually
| does - what is causes the workstation to do in a domain environment.
| I know it clears out the workstation resolver cache - but I am more
| curious as to the impact this has in a redirected folder scenerio

It does nothing more than flushes a Domain-Name cache on the PC.

ok - then what are the sequence of events that follows - meaning what
steps does the PC take after a DNS flush? And are those same events
initiated by a DHCP release/renew?

 

[David H. Lipman]

From: <[email protected]>


|
| ok - then what are the sequence of events that follows - meaning what
| steps does the PC take after a DNS flush? And are those same events
| initiated by a DHCP release/renew?

No, it has nothing to do with DHCP.

After the cache is flushed, it will again be populated based upon Domain-Name queries to a
DNS server.

 

[lwardle]

The reason I'm asking is for the following scenerio:

Our workstations currently will randomly and completely unpredictably
take an hour or more to fully render the desktop icons on roaming
profiles. We've done all the usual responses to this issue and
currently the only thing which fixes it is to log onto the workstation
as local admin - do a release/renew of DHCP and log back on as the
user. The desktop renders normally and quickly and life is good until
it happens again. Recently we discovered that flushdns whilst logged
on as local admin fixes it. So now we are trying to determine what
possible workstation/domain/network functions could be kicked off by
either of these two commands. And what of these functions the two
commands have in common.

Does this ring any bells or make sense?

 

[David H. Lipman]

From: <[email protected]>

| The reason I'm asking is for the following scenerio:
|
| Our workstations currently will randomly and completely unpredictably
| take an hour or more to fully render the desktop icons on roaming
| profiles. We've done all the usual responses to this issue and
| currently the only thing which fixes it is to log onto the workstation
| as local admin - do a release/renew of DHCP and log back on as the
| user. The desktop renders normally and quickly and life is good until
| it happens again. Recently we discovered that flushdns whilst logged
| on as local admin fixes it. So now we are trying to determine what
| possible workstation/domain/network functions could be kicked off by
| either of these two commands. And what of these functions the two
| commands have in common.
|
| Does this ring any bells or make sense?
|

The scenario is not familiar and I have no advice -- sorry. :-(

 

[Kerry Brown]

Are both the DHCP and all the DNS servers AD integrated? In other words is
there a router doing DHCP or a second DHCP server on the network? Are the
clients only using an AD integrated DNS server, not a router or an ISP's
server?