Thank you for your patience.
We performed further research and have some new findings.
1. When the computer in domain network (IP address: 10.x.x.x), it has valid
DNS and IP address, and it can locate AD and DFS related servers via DNS
2. We noticed when the issue occurs, the problem computer gets IP address
(192.X.X.1 ) from a DHCP, but no DNS and WINS. Therefore, as what we can
see in the network trace package which you provided previously, the
computer keeps performing NetBIOS name resolution request via broadcasting.
As you know, broadcast traffic will not be routed. As a result, the
computer cannot get a valid response.
Given the situation from these information, I suspect that the issue is
related to name resolution. Here are our suggestions:
1. Please let me know the network topology. For example, is there a router
between your domain network and 192.x.x.x subnet? How are these two
sub-networks connected? Also, is there DC or DFS Root target server in the
2. I also noticed that you mentioned everything starts to work correctly
after restarting the computer. It is a bit abnormal. Could you please run
"ipconfig /all" before and after restarting computer? If the computer is
able to get a valid DNS server from the DHCP server after restart, it would
be able to locate AD and pull necessary information regarding the DFS
3. Also, please try to access DFS by using \\w####t.nl\<DFSRootName>
instead of using \\W##\### (domain NetBIOS name). How it works in different
scenarios (before and after restart, in the new network)?
4. Did you enable INSITE option for the DFS namespace? If yes, the DFS
client will not access DFS target servers in other sites, and may cause
similar problems. Please have a look.
5. Meanwhile, I would like to let you know that this is a complicated issue
and is related to server components. (This newsgroup is mainly focus on
Windows client.) I will continue to do my best to help you on checking some
basic settings and mainly focus on the Windows XP side. However, please
know that we may still suggest contacting Microsoft CSS for further
investigation in the future, to ensure your are best served. Thank you
for your understanding.
Again, thank you for your time and efforts on the issue.
Hope it helps.