SEP Not letting me install giving me a firewall error...

[Migration User]

The Firewall is off, yet, I get this, and why don't I ever get SEP_INST.LOG files anymore on client installs???? The Service is also disabled, and I used CleanWipe...still a no go./..

[Thomas K]

See if this KB can offer any help.

Error: "No Network Provider accepted the given the network path"

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/3e95d7f0ebf56f6088257393005bd82b?OpenDocument

Best,
Thomas

[Migration User]

In Windows 2000/XP/2003 you have the possibility to disable NetBIOS over TCP/IP. You do this by right-clicking on My Network Places and selecting Properties. Then right-click on the appropriate Local Area Connection icon, and select Properties.

Next, click on Internet Protocol (TCP/IP) and Properties.

Now click Advanced, and select the WINS tab.

There you can enable or disable NetBIOS over TCP/IP.

No restart required...

 

[Migration User]

I have not changed it, still a no go.

[Migration User]

Still does not work.

[Rafeeq]

Hello Bryan, what is that firewall error ? port 445?
do a search for SEP_Inst.log file. in temp and windows temp, should be there, if the install ever ran.
if you dont get it . enable msi logging paste the log file (10 lines above and below return value 3)
http://support.microsoft.com/kb/314852 

445 id used for file and printer sharing make sure you have that enabled.

[Migration User]

Reg_SZ: Logging
Value: voicewarmup

There is a Reg_SZ  key already there for Logging, and the value is iweap....do I need to change that???????

[Migration User]

Try running the netstat command and check whether port 445 is listening or not

[Rafeeq]

take a backup of registry,

the values should be

Reg_SZ: Logging
Value: voicewarmup
 Yes change it , run the install now we should get a log file.
what error msg do u get when you run the install locally? 

[Migration User]

Neither is selected...

[Migration User]

The NetBIOS trick worked, I misread it earlier.
Thanks again.

[Migration User]

No good...

[Migration User]

There is NO logfile for SEP_INST. I did what you instructed, and there is no log file.

[Migration User]

Logging is a no go, install it puts the files in and dissappears INSTANTLY....

[Rafeeq]

Not a problem Bryan.
able to create a log file?
are you trying push install or installing it local to the box? 

[Migration User]

I followed the instructions, and nothing...I am using the push deployment wizard and pushing a package to the PC, it goes to the PC for like 5 seconds, and the files are instantly removed. I have tried EVERYTHING in this post, and NOTHING works, logging, or installation.

[Thomas K]

You might want to open a case with Symantec support to help you get to a solution quicker. You can continue working this issue through the forums as well.

http://www.symantec.com/business/support/contact_techsupp_static.jsp

Thomas

[Migration User]

Try by resent windows firewall using Netsh firewall reset command. If not helps refer the below articles Troubleshooting Windows Firewall settings in Windows XP Service Pack 2 for advanced users http://support.microsoft.com/kb/875357 You cannot start the Windows Firewall service in Windows XP SP2 http://support.microsoft.com/kb/920074/

[Migration User]

Same Behavior. Also, the second step turned the firewall back on. I want it to be disabled.

[Migration User]

...or upgraded to SP3. No matter what I try. Not one of the listed solutions work, and I am spending way too much time on this one machine.  If that doesn't work, I will either call Symantec or have that machine re imaged.

[Migration User]

 Once you enable MSI logging it will create the logs in either %temp& or c:\windows\temp
the name of the log will not be SEP_INST you will have to find out with latest modified log.

For any install failure the best way is to get the logs..Even if you call symantec they will do this..rather than shooting in the air..

[Migration User]

Try this. 
Go to the machine that port 445 is not working on.
Start -> Run -> CMD

In the CLI type "NETSH INT IP RESET LOG.TXT"  <enter>

Should return you a CLI with NETSH>

Simply reboot the computer.

This will reset the entire TCP/IP stack on your machine to factory default.  If there are any problems in the stack it will be rebuilt and should aut-correct itself.

****
NOTE
****
If you have a static IP address on 1 or several NICs in the machine, you will have to re--allocate them.
If you are using DHCP you should be fine.

[Migration User]

How am I supposed to know what it is called???

[Migration User]

I finally have to give up on this one, like Vikram mentioned, shooting in the air is counter productive. I will call them and hopefully we can get this issue addressed accordingly.

[Migration User]

Man, these are all great, but nothing works.

[Rafeeq]

what I can tell here is that , the installation never ran so no logs. isn't it?
not sure if you tried to run locally and tried to get the logs if any and analyzed it.
if it runs locallay then the problem is with remote install
may be a gpo not allowing the exe files to get executed or not enough space or security concerns.again a speculation which would definitely lead us somewhere.

[Migration User]

Rafeeq, 20 other machines have taken this SAME EXACT sequence without this much of a problem. It is machine specific. No logs, the files go to the clt-inst folder, and pretty much are gone within the blink of an eye, all three files are sitting there, then if you turn away for one second, the folder ONLY contains VPRemote. The Disk space is adequate. This machine is also in the same AD OU as the other 20 previous roles. GP should be NO different in this case.

[Rafeeq]

It has to be somethng sir...
anything in event viewer

[Migration User]

I appreciate your strong effort greatly, but I will wait to hear back from Symantec. I am sure it is something they will fix in less than 5 minutes. I will advise of progress.

[Migration User]

The Technical support person from Symantec said it had something to do with the LiveUpdate, so I needed to copy the "SEP" folder over manually and install it this way, then copy the sylink.xml from the server to the client to get it to report to the correct client group. This did work, but was not really what I was looking for. I really wanted the push to work accordingly. He also mentioned that the DCOM permissions needed to be adjusted. It works now, but I really hope NOT to come across this type of issue again.
Thank  you.

[Rafeeq]

As I mentioned earlier, you can always install it manually
I know you did not wanted that, 
why do u install liveupdate and replace sylink
cant you just export a package and run it locally on the box.so that you dont need to run sylink over and over again? cant that be done?
I think the tech was taking about launch permissions in Dcom.

 

[Migration User]

Copied the package to the PC itself and it failed that way as well. We had to copy the installation over from CD1 the "SEP" folder and install it that way. Really frustrating, but it is now working. I REALLY hope to NOT come across this type of issue again.
1. Instaled LiveUpdate (which took forever).
2. Installed SEP.
3. Copied the Sylink.xml to get the correct group association.

[Rafeeq]

i forgot to mention this before
when you create the package
uncheck the single exe package
by this you will get expanded msi package
you can copy this and place it in client machine
install liveupdate inside the package
run the setup next
so that you dont need to copy the sylink file again.
helpful??

[Migration User]

Is this hardened OS ? any special security settings being done on them ?
With Windows 7 microsoft has gone even more crazier about security than they were with Vista..
It will take some time for everybody to adjust with this OS..even Symantec..

There has been many threads about WIndows7 remote install issues some solved some agreed with above or similar so called Work Around...
It has been seen in few cases once you re-image your System deployment works..why,how nobody knows..a deep root-cause analysis is required for this issue..

[Migration User]

Don't understand that sir.

[Migration User]

This was an XP machine, same image as every other PC that took the install sucessfully. I have insalled on 4 Windows 7 machines with no issues.