Healthcare Online User Group

Hello Symantec community. This is a strange one that has suddenly started to happen on our SEPM servers. When I go to push a client via the SEPM console, it does not find the correct PC name or IP address on our network. It actually resolves to an entirely different PC.

For example, I'll use nslookup from the SEPM server to look up XXXXX PC name and I confirm in DNS that it is indeed xxx.xxx.xxx.xxx IP, yet SEPM resolves to an entirely different PC name. If I try to push out via IP address the same thing happens, it resolves to a totally different PC name, which is incorrect according to our DNS. It is like the SEPM servers have some kind of cached/out of date DNS. I have flushed DNS, rebooted multiple times, etc. Is there some kind of cached DNS happening on these servers?

Where is this hanging up at? This has never happened and is quite hindering to us suddenly. I basically can't push out managed clients to new/restaged PCs. I recently did a migration to a new SEPM server and get the same thing. Maybe this is because old/cached data came over from the original SEPM server?

Help! Thanks much --Kirk

hi,

Yes I have seen this problem, seems you are right? Sorry I do not have any idea about why it shows like that?

Any one have any clew about this issue?

Hi,

This issue not related for SEPM.You need to enable DNS Scavenging in your DNS server..

Understanding Aging and Scavenging

http://technet.microsoft.com/en-us/library/cc771677.aspx

Set Aging and Scavenging Properties for the DNS Server

http://technet.microsoft.com/en-us/library/cc753217.aspx

I'd actually be more inclined to investigate your WINS/NetBIOS settings and disable these if no longer in use.

As you're getting the correct results via nslookup (and presumably ping and ping -a) it doesn't sound like a DNS problem.

Hey Brian, I have not contacted support yet as I've recently been out and playing catch-up on tings and hoped maybe the forum would resolve for me!

I just installed the latest version v12.1.4104.4130.

I see some of the other replies but I can't imagine our DNS is "jacked" as this is the only thing we are experiencing in a nagative manner. This literally just started happening a few weeks ago before I left for some vaca.

Any ideas outside of a global DNS issue? Thanks!! --Kirk

Thanks for the reply. I'll take a look at the documents and see if anything applies.

I'm not 100% that it isn't just a SEPM issue as we are not experieincing other issues with DNS, etc. It appears to only be SEPM that has the issue with resolving properly.

I post back if I have any other questions about the articles if that is cool. Thanks again --Kirk

Hello, not 100% sure where or what you may be speaking of. I assume on the SEPM servers?

I've posted a screenshot from the TCP/IP properties for the NIC. What woul I change here? What impact would that have exactly? Why is this suddenly an issue!?

Thanks for the help --Kirk

Essentially the WINS/NetBIOS bit is used for the "Browse Network" tab of the Deployment Wizard.  Is this the section that's giving the wrong results?

Also, are you running the Deployment Wizard directly on the SEPM itself, or via the Java/Web Remote Console?

Yes, this is exactly where I am trying to push clients out. Once I type a PC name or IP address in the screenshot below, it then retrieves the wrong PC to push to.

This happens from both the SEPM console and the Java interface. It happens on both SEPM servers too.

Thanks for the continued help!! --Kirk

Does using the client machine's FQDN make any difference?

Also, have you trued using the Push Deployment Wizard (called ClientRemote.exe) found in the Part_2 download from FileConnect under \Tools\PushDeploymentWizard?

This is essentially the same tool, but outside of the SEPM console.  Can you advise if this results in the same issue?

Hmmmm, oddly enough, that actually worked....using the FQDN.

It also worked via the ClientRemote.exe program instead of the Deployment Wizard.

What does that mean!? Thanks!!

Just to clarify, the ClientRemote.exe tool using hostnames only works correctly?

The ClientRemote.exe tool is a windows program rather than a Java one, so perhaps the Java properties are using a different DNS Suffix order/list?  I've not seen this one myself, but that's where I'd personally focus on first.

I'm glad you're working fine with my workaround though! 

I used the clientremote.exe first with the FQDN and that pushed successfully. I then went back to the SEPM console and used the wizard (like I normally do) and that suddenly is working with just the host name, not FQDN. Or at least did on the 3 PCs that I had trouble with recently.

I mean that would make no sense that the clientremote.exe triggered something in a positive way that SEPM is now able to push successfully. Then again, this world doesn't always makes sense!

For now, I'll mark your post as a solution...since indeed the clientremote.exe worked successfully right out of the gate on PCs I was having trouble with via the Deployment Wizard in SEPM.

Thanks a ton friend...