Jump to content
doudz

Wins Stop Working

Recommended Posts

I have installed Immunet 3.0.8.9025 on Windows XP SP3 (with windows firewall disabled) and names resolution using WINS server is not working anymore.

 

Test :

 

With Immunet 3.0.8.9025

C:\Documents and Settings\Administrateur>nbtstat -A 192.168.200.206

 

Connexion au réseau local:

Adresse IP du noeud : [192.168.200.16] ID d'étendue : []

 

Hôte introuvable.

 

 

Without Immunet

C:\Documents and Settings\Administrateur>nbtstat -A 192.168.200.206

 

Connexion au réseau local:

Adresse IP du noeud : [192.168.200.16] ID d'étendue : []

 

Table de noms NetBIOS des ordinateurs distants

 

Nom Type État

---------------------------------------------

JASV06 <00> UNIQUE Inscrit

JASV06 <03> UNIQUE Inscrit

JASV06 <20> UNIQUE Inscrit

..__MSBROWSE__.<01> Groupe Inscrit

JANIN <1D> UNIQUE Inscrit

JANIN <1B> UNIQUE Inscrit

JANIN <1C> Groupe Inscrit

JANIN <1E> Groupe Inscrit

JANIN <00> Groupe Inscrit

 

Adresse MAC = 00-00-00-00-00-00

 

I tried several machines and virtual machines (virtualbox) with Windows XP SP3, and I got the same problem.

 

So this release is unusable in corporate environnement.

 

I tried the release 2.0.17.31, and there's no problem.

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

you are right. We got a similar problem, not only the wins support seems to be deactivated, the netbios broadcast name resolution is also deactivated. This error happens since 3.08.9055, with 3.06 everything is working good. You can maybe bypass it temporally by using DNS entries for the important servers.

 

Cheers

silc

Share this post


Link to post
Share on other sites

Mmm! "This could very well be some kind of new bug" with the newest 3.0.8.9025 build of Immunet so I'm not certain that this applies to you gentlemen but conflicts with other antivirus packages have been reported when more than one DHCP server is present in a networked enviroment. The conflict happens when there's multiple lookups for the same IP address and a scan loop occurs. You are more than welcome to submit a SDT Report http://forum.immunet...ic-tool-report/ directly to support@immunet.com if the issue persists. Also, here is a Microsoft Knowledgebase article that might be helpful regarding the issue of virus scanning using an Enterprise enviroment. http://support.microsoft.com/kb/822158 Speaking of Enterprise, Sourcefire does have quite an inovative and comprensive security solution specifically taylored to such an enviroment with numerious endpoints. It's called FireAMP! http://www.sourcefir...tection/fireamp Best wishes, Ritchie...

Share this post


Link to post
Share on other sites

Thanks for your answer. I tried other dhcp server and finaly static ips. Nothing solve the problem. I think the problem is udp port 137, after the installation this port is blocked.

 

Sincerely,

Silc

Share this post


Link to post
Share on other sites

Thanks for the feedback silc. Much apreciated. Did you send in a SDT report? If you haven't already I would encourage you to do so. I ask this because this is definetly something support/development needs to look into further in my view. In fact I'll Private Message some folks about this if a responce isn't soon forthcomming. Best wishes, Ritchie...

Share this post


Link to post
Share on other sites

Hi all,

 

doudz would you mind sending a support snapshot to support@immunet.com. Instructions on how to generate a support snapshot can be found here:

http://support.immunet.com/tiki-read_article.php?articleId=10

 

I will confirm but this sounds like a bug that was discovered that affects Immunet 3.0.8.9025 on Windows XP and Server 2003 only. We have found the root cause of the bug and are in the process of testing the fix, the fix will be in the next release of Immunet Protect.

 

Best regards,

 

Anthony

Share this post


Link to post
Share on other sites

I can confirm this. WinXP sp3 connecting to a window NT4 domain (seriously!) with Immunet 3.0.8.9025 (same version of immunet). We were testing it on one machine before rolling it out. Guess we're not rolling it out.

 

A slight variation -- when I installed it, the machine did not ask for a reboot, so I left it. The user worked with the machine all day. The problem only cropped up after the machine was shut down. After removing immunet (complete removal) and restoring function to the machine I manually added the wins servers to the networking config, then re-installed immunet and had the same failure after reboot. removed immunet and fault cleared.

 

I've generated a support snapshot Immunet_Support_Tool_2013_03_27_09_47_44.7z and am emailing it to the support address.

Share this post


Link to post
Share on other sites

Much apreciated bisi. Thanks for the input and I hope the SDT report you submitted helps in squashing this bug once and for all! The next build of Immunet should address this Netbios Name Resolution conflict. Crossing my fingers the next build is soon forthcoming. Time will tell.

Share this post


Link to post
Share on other sites

This is biting my enviroment too where a few XP machines and a 2003 server still exist; is it possible to downgrade Immunet, or force the installer to a previous version? Thank you

Share this post


Link to post
Share on other sites

Since Immunet uses a bootstrapper installer you automatically get the newest version that supports your language. However I would suggest you email support (support@immunet.com) to see if they can provide you with an off-line installer for an earlier version that does not have the netbios name resolution bug. It will be nice when this bug is put to rest for good with the next build of Immunet. I have no ETA as to when that will be though.

 

Best wishes, Ritchie...

Share this post


Link to post
Share on other sites

For those that are fighting with WinXP version in a workgroup/HOME network and still not reaching other WinXP Professional machines through Network Neighborhood/My Network Places there is a work around that I use. I could ping the IP of the the WinXP Pro without problem. I could not reach it by directed name,by nbtstat of IP or network name, or by net view \computer name. So I setup my local workgroup router DNS to register the computer name and IP of all machines in my workgroup. Then I could use net view \\computername and reach the WinXP Pro machine. Next I did a RUN \\computername and Explorer opens with the shared file folders and printers of the WinXP Pro machine. From there I created shortcuts by the shared folder name and put them first on my Desktop then in moved them to My Network Places folder. Now I can open and reach the shared folders of the WinXP Pro machine, even though when I View Workgroup Computers the WinXP Pro machine still doesn't show. Hope this helps others until the bug fix for WinXP Pro is available.

  • Like 1

Share this post


Link to post
Share on other sites

Interesting workaround bvamunds! Thanks for the input. Perhaps other Win XP Pro/Server 2003 users will benifit from this info until the new version is rolled out.

 

Cheers, Ritchie...

Share this post


Link to post
Share on other sites

Hello. Yes, experiencing this name resolution issue with Win2k3 Server Enterprise. It's no biggie as IP works fine, more of an annoyance than anything. Will gladly donate to have this bug squashed :)

Share this post


Link to post
Share on other sites

Hi rretamar, thanks for the input on the 3.0.12 build. If you read the other threads to this topic then you know that Support is quite aware of this name resolution bug. However you are welcome to send a SDT report to Support if you wish. http://forum.immunet.com/index.php?/topic/1672-how-do-i-submit-a-support-diagnostic-tool-report/

 

There is a new version in the works that will have a number of changes including addressing this bug. I don't have an exact time frame when this version will be released, hopefully soon. Keep an eye on the Announcements section of this forum would be the best advice I could give you.

 

Cheers, Ritchie...

Share this post


Link to post
Share on other sites

Hi,

 

I confirm the bug is still here on release 3.0.12.9412 BUT not all the time. On my WinXP SP3 at the first boot the bug is here then I reboot and it magically works !

 

Any news about a newer version ?

To me this bug is the last step before moving my company from Avast to Immunet.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...