Hey ya'll...really really hoping someone here can help...I am trying to sort out what at first was a minor issue and in trying to fix it I have now made a bigger issue sadly...Initial issue was that in this small office network with a mixed environment with 10 workstations and 1 2003 sbs server that on workstations when files were downloaded over the internet certain small files were taking a very long time....issue did not seem to be speed and it was only mainly with our remote software exe...client unhappy....what we would do as a work around was ask them to try on their server and the same file would install quick and we would simply allow them to access this exe via their network...i was doing an ipconfig on a workstation and noticed that the primary DNS suffix was stating frontiernet.net not domain.local I reasoned that clients must be having a dns issue with their server...I tried setting the server primary dns to itself (before it appears to be a public dns ip) and the secondary to the router on the network...if I do this the server cannot connect to the internet...If I make the server dns the primary and then make the secondary the dns my router is using from my isp my server is able to get online...been playing with this a little...when i try to ping my server by computer name from a workstation while I get replies it is completely unexpected...it replies back as follows:
server.frontier.net
which is unexpected and a completely different ip than the server actual ip also their isp is optimum not frontier?? under ipconfig my connection specific dns suffix is again server.frontier.net?? I tried dnsflush reregister dns etc...At first my dcdiag
/testdns had some failing forward zones and root hints but those are all passing now on the server end...not sure whats going on here if i ping from server to workstation computer name it gives a different ip address and then times out??? Sounds like some
old records need to be erased then records refreshed? I am at a total loss any help is much appreciated basically burning midnight oil here will be happy to post any info or logs thanks!
actually this can be closed yay! ok posting my solution i am still researching this nutty issue ok here is what i figure so far...this all happened because client request his current av be uninstalled and a new one installed seems like a few files may have got deleted with the vault still trying to figure this out anywho little did i know when i restarted their server their domain dns server was no longer up i never realized because in win 7 it says you are always in domain just takes awhile to login and i could still access the server by server name in run...this is because i did have share access but the domain was still down i used the dcdiag.exe /testdns fix dns and netdiag commands to pin it down then i had to edit settings in my dns server forward lookup zone and host file...once that was done dis-joining rejoining domain seemed to do the trick once all was passing on server...nuttiest issue though...when i would ping the server name i would get a response from frontiernet.net thought their isp is optimum and the server was a totally different address i still don't understand this it seems prefilled in the router as well can't be changed apparently unless they request static account according to isp their support seemed baffled as well why router was pulling frontiernet.net from their modem but once the dns server was up all was well hope this helps someone