I've got a VM running Windows 2003 which is running both IIS and Apache (don't ask me why - it predates me working here) and for a long time, name services to that box via the name \\svnserver were working great. A few weeks ago, we rebooted that server and ever since then, reaching it via WINS name is totally tanking, but via IP works fine.
For this fix, lets pretend that \\svnserver's IP address is 192.168.111.201 (not actually the IP, but for this purpose, it works).
I've gone into the local name servers and both of them are running WINS. Navigating to that box from Windows Explorer for for file sharing works like a champ, but SVN just hangs using WINS resolution. We never even get an error, it just hangs and eventually the SVN client crashes.
That client version is TortoiseSVN 1.8.7, Build 25475 - 64 Bit
SVN server version is VisualSVN v1.8.10
I've verified that \\svnserver is using the correct IPs for the WINS configuration, and I verified that the DNS entry on the WINS servers is in the list and working. I also took a look @ our SonicWall's DNS settings - they're good. We built and any/any rule to make sure that inner-LAN stuff can get around without issues. The server can reach the internet, but we just can't navigate there via SVN
I've even run an ipconfig /flushdns on the client and all of the servers involved as well as dumped the Sonicwall's DNS cache to see if it would resolve. Nothing changed. Works great via IP, but tanks when name services are used.
This isn't a huge issue, but my buddies in the other departments who depend on this service aren't greatly savvy and the WINS names are a lot easier to remember.
I'm honestly worried that IIS is causing this whole stupid issue as SVN is Apache based and I'm thinking that the reboot screwed up something that is now causing Apache and IIS to fight over the name resolution. Problem is that my knowledge of how IIS functions is somewhat limited. I get that it's a web service that has some shiny features, but if it is getting in the way, I'm more than willing to get rid of it.
Anyone else encounter this insanity or have any ideas about how to correct the problem? It's not business critical or anything, but it would be really nice to spend a day not getting asked what the server's IP was fifteen times before lunch.
EDIT: I was able to fix this by rebuilding the name servers. Thanks anyway guys.
More about :
svn found dns works fine