I have a terminal server (Server 2008 x64) that at times - can''t reach a share on an applciation server in teh background.
AppServerA is the applciation server with a share called ShareA with Everyone Full Permissions. On a domain (of course) and domain controllers are 2003.
Terminal Servers A-D all access ShareA on AppServerA for use in a third party program.
Occasionally the clients that connect to TerminalServerA will call stating they aregetting errors trying to access ShareA.
The third party program throws an error about not being able to access teh destination \\AppServerAIP\ShareA (So \\172.16.0.2\ShareA)
Next step is logging into TerminslServerA and clicking Start then RUn and doign a \\172.16.0.2 and clicking OK. It says it is unable to reach server. (Although you can ping it from that server and on TerminalServerB-D - they all can)
I'm used to seeing \\HOSTNAME not resolving - being a DNS issue but not \\IP
So far the only workaroudn we have found is to boot the offending TerminalServerA. When it comes back up - it can resolve \\172.16.0.2\ShareA.
Booting AppServerA does nothign to the scenario.
No errors in TerminalServerA Windows Error Log
Have tried removign server from domain (back to workgrouop) and putting it back on Domain
Have tried the same thing but also change the COMPUTERNAME but no help.