Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NAV10CE subnet problem

Status
Not open for further replies.

cricket

Technical User
Jul 5, 2000
361
IE
I have 2 subnets being serviced by SAV10.

The server acts as virus server, mailserver (MDaemon) and internet access control (Wingate).
It has 2 NIC's one for the outside world and the other internal with an IP of aaa.bbb.45.100

All computers on the aaa.bbb.45.* subnet (same as server) work fine for email, internet, and virus updating.

The computers on a aaa.bbb.44.* subnet are fine for email and internet access, but not for communicating with the server. I can install the clients remotely on this subnet, but updates are not working. Routing seems OK.


Is there an issue with 2 NIC's in the NAVCE10 server?

Or is it something else? I would welcome suggestions.
 
SAV only likes to talk to computers at the side of 1 NIC... not 2. It sounds like you have SAV server listening on the internet... that's just bad in my opinion.

I recommend using a decent VPN solution, and clients on the outside world should be able to check in with your server just fine. It is way more secure as well...
 
I finally found a resolution on the Symantec website
Document ID:2002091816400248

Title:
Communication problems with a parent server with more than one Network Interface Card



Solution is by adding information to the Client registry to point the client to the correct Parent IP address.

· To create the ParentIPAddress registry key

1. On an affected client, use the Registry Editor to find the following key:

HKEY_LOCAL_MACHINE\Software\Intel\Landesk\VirusProtect6\CurrentVersion

2. Click Edit > New > String Value.

3. Type ParentIPAddress for the name.

4. Click Edit > Modify.

5. Type the IP Address for the internal NIC.

6. Exit the Registry Editor.

Restart the computer for changes to take effect

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top