Very strange name resolution issue.
We are not running a client configured vpn. We are running a permanent firewall to firewall vpn. The clients don't even know they are communicating across a vpn. I will look at the Process Monitor information to see if it can be of some help, otherwise this post is not much help to me. Exactly what good is setting up the dns suffix going to do for me? The client can ping everything by name all the time except this one server. Please explain further the purpose of doing this. Does anyone have anything else to help me out. thanks
July 13th, 2011 8:58am

I will try to make this as clear as possible. I have a user at a remote site running Win 7 Pro SP1. It is a part of our domain just like all other systems on our network as the remote site is connected to our main site by permanent full time vpn. Lets call the remote system Mike. Mike uses autocad and gets a license from a license server up here at our main office. For the last 2-3 weeks Mike has been getting an error between 5:00 and 6:00 pm due to losing connectivity with the license server. He tried to ping the server and gets the following error: "Ping request could not find host poly-gonbu. Please check the name and try again." So I checked his nic and updated the driver, ran windows update, etc etc and everything looked good but it still kept occurring. So then I set up a batch file to run several times per day but more often between 5:00 and 6:00 and I set it up to ping 3 different servers up here and append the ping results to a txt file so I could check it later. I also setup the same batch file to run on my computer (that is here at the main site, not where Mike is). Mike is still failing at different times between 5:00 and 6:00 pm nearly every day but mine never fails to ping the license server. Mike can ping the license server by ip address at all times. I tried to ping from another computer at the remote site while Mike was experiencing the issue and the other computer can ping the license server by name without a problem. So it appears to be some type of name resolution issue. It is only happening to his computer and it only happens between 5:00 and 6:00pm and it is only happening with the one server. Someone please put me out of my misery and tell me I am in the twilight zone. What the heck could be happening???? HELP!! thanks already
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 9:06am

bump
July 13th, 2011 9:14am

Hi, Thanks for posting in Microsoft TechNet Forum. As this issue only occurs between 5:00 and 6:00 PM, I suspect this is related to some scheduled tasks or pre-defined programs, please verify if you have this situation in your environment. And I suggest you launch process monitor to capture the process log to see if you can find more useful information: Troubleshooting with Process Monitor Meanwhile, according to your description, you could ping successfully via IP address; you could use the FQDN to check how it works. To do this, manually configure the DNS suffix for the TCP/IPv4 address in the VPN connection: 1. Go to network connections. 2. Right-click the VPN connection that you want to configure, and then click Properties. 3. If you are prompted to confirm that you want to continue, click Continue. 4. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 5. Click Advanced, and then click the DNS tab. 6. Specify the DNS suffix for the connection, and then click OK three times. Hope it helps. Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2011 11:03pm

Hi, Sorry for my misunderstanding on your VPN connection. And it seems that you have not found anything in process monitor. Please use nslookup tool on Windows 7 machine and check if you are able to resolve names at that specific time. I think it should work as other computer has no such issue. If that works, it seems DNS cache is corrupted, because ping cannot get the right IP address to contact. Reset DNS client service to check how it works. Meanwhile, it also seems like that something is blocking packets on Windows 7 machine. As I said, this would be related to some scheduled tasks, have you checked your programs running in Windows 7? Try to boot Windows 7 into safe mode with networking and check how it works. Alex Zhao TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 13th, 2011 11:07pm

If the license server is always available when addressing it via IP address you could add a entry to the local hosts file on the machines at the remote site, bypassing the need to talk with a DNS server, to serve as a work-around. As for a more permanent fix, you will likely need to take a look at your firewall logs to see what is happening to the packets for the DNS request when its attempting to resolve the FQDN or hostname of the license server. - Jason
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2011 1:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics