Hey all,
Lately I've been having a strange issue with my local network. A few years ago, I named my domain tavis.com (which I realize now I should have named is to something like tavis.local or something else that isn't registered as a web domain - because Tavis.com is an actual website, not one that I own). However, this domain is behind a school firewall/router and behind one of my own routers, so therefore I didn't figure it would cause much of an issue or need to change it immediately.
However, recently, I have noticed in BOINCView that sometimes a few PCs to about ALL PCs reporting to BOINCView are not reporting correctly because the PCs running BOINC have been having trouble resolving the NetBIOS name of my DC or other PCs on my local network to local, private IPs. My main DC, the celeron-1700 system, is the main problem. When I try to ping the systems by NetBIOS name that are NOT reporting in BOINCView, the system is pointing to the tavis.com (website) public IP. Screenshot
However, my secondary DC, the cisco-3431, can ping every NetBIOS name properly. I am not sure what happened to my primary DC to cause these problems as I have not changed anything with DNS or AD.
Both DCs have local private 192.168.1.x IPs listed in the DNS Management tool for each host and pointer record, none point to the 72.163.48.x IP.
The only thing I can think to do is check my DNS settings for something I have missed. Barring that, demoting my primary DC and redoing it completely.
Some hosts on the local network are having trouble pinging to other NetBIOS computer names also.
As for my DC's:
Primary:
Win Server 2003 Std. SP2
IIS, FileZilla, DNS, AD
Secondary:
Replicating primary system
Win Server 2003 Std. SP2
DNS, AD
Thanks for any help/suggestions.
Lately I've been having a strange issue with my local network. A few years ago, I named my domain tavis.com (which I realize now I should have named is to something like tavis.local or something else that isn't registered as a web domain - because Tavis.com is an actual website, not one that I own). However, this domain is behind a school firewall/router and behind one of my own routers, so therefore I didn't figure it would cause much of an issue or need to change it immediately.
However, recently, I have noticed in BOINCView that sometimes a few PCs to about ALL PCs reporting to BOINCView are not reporting correctly because the PCs running BOINC have been having trouble resolving the NetBIOS name of my DC or other PCs on my local network to local, private IPs. My main DC, the celeron-1700 system, is the main problem. When I try to ping the systems by NetBIOS name that are NOT reporting in BOINCView, the system is pointing to the tavis.com (website) public IP. Screenshot
However, my secondary DC, the cisco-3431, can ping every NetBIOS name properly. I am not sure what happened to my primary DC to cause these problems as I have not changed anything with DNS or AD.
Both DCs have local private 192.168.1.x IPs listed in the DNS Management tool for each host and pointer record, none point to the 72.163.48.x IP.
The only thing I can think to do is check my DNS settings for something I have missed. Barring that, demoting my primary DC and redoing it completely.
Some hosts on the local network are having trouble pinging to other NetBIOS computer names also.
As for my DC's:
Primary:
Win Server 2003 Std. SP2
IIS, FileZilla, DNS, AD
Secondary:
Replicating primary system
Win Server 2003 Std. SP2
DNS, AD
Thanks for any help/suggestions.
Facebook
Twitter