SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
BackupPC on VLAN
Author Message
Post BackupPC on VLAN 
Hi guys,

I have setup backuppc running on Centos5.7. I have a vlan setup with different subnets. Am trying  to resolve the computer names by name hence using nmblookup. Am only able to resolve the machine on the same subnet as the backup server. I can ping machines on the other subnets but when I try to resolve their names, am unable. Then I decided to add virtual networks to the backup server of the subnets. Upon doing this, was unable to reach the other networks.


Could you help PLEASE.

--
RegardsKevin 

Post BackupPC on VLAN 
On Tue, Jan 17, 2012 at 12:11 AM, Kevin Kimani <kevinkimani < at > gmail.com> wrote:
Hi guys,

I have setup backuppc running on Centos5.7. I have a vlan setup with
different subnets. Am trying  to resolve the computer names by name hence
using nmblookup. Am only able to resolve the machine on the same subnet as
the backup server. I can ping machines on the other subnets but when I try
to resolve their names, am unable. Then I decided to add virtual networks to
the backup server of the subnets. Upon doing this, was unable to reach the
other networks.

Could you help PLEASE.

The best approach is to set up DNS with either static IPs or a system
that lets the DHCP-assigned machines register their addresses
dynamically. Next best is a central WINS server (the DHCP server
gives out it's address and you can use samba on the backuppc server if
you don't have another suitable machine).

But, if you have connected a VLAN trunk to the backuppc server and
given it an interface and address on each of the relevant VLANS,
nmblookup should be able to find everything with broadcasts. I don't
understand your problem with other networks, but it is probably simple
routing. Be sure the netmask is correct for each interface and that
you have only assigned one default gateway (i.e. the new VLAN
interfaces should probably not have a GATEWAY entry).

--
Les Mikesell
lesmikesell < at > gmail.com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Post BackupPC on VLAN 
Thanks Les, It did work. 

Warm Regards

On Tue, Jan 17, 2012 at 9:38 AM, Les Mikesell <lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])> wrote:
On Tue, Jan 17, 2012 at 12:11 AM, Kevin Kimani <kevinkimani < at > gmail.com ([email]kevinkimani < at > gmail.com[/email])> wrote:
Hi guys,

I have setup backuppc running on Centos5.7. I have a vlan setup with
different subnets. Am trying  to resolve the computer names by name hence
using nmblookup. Am only able to resolve the machine on the same subnet as
the backup server. I can ping machines on the other subnets but when I try
to resolve their names, am unable. Then I decided to add virtual networks to
the backup server of the subnets. Upon doing this, was unable to reach the
other networks.

Could you help PLEASE.



The best approach is to set up DNS with either static IPs or a system
that lets the DHCP-assigned machines register their addresses
dynamically.   Next best is a central WINS server (the DHCP server
gives out it's address and you can use samba on the backuppc server if
you don't have another suitable machine).

But, if you have connected a VLAN trunk to the backuppc server and
given it an interface and address on each of the relevant VLANS,
nmblookup should be able to find everything with broadcasts.   I don't
understand your problem with other networks, but it is probably simple
routing.  Be sure the netmask is correct for each interface and that
you have only assigned one default gateway (i.e. the new VLAN
interfaces should probably not have a GATEWAY entry).

--
 Les Mikesell
   lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net ([email]BackupPC-users < at > lists.sourceforge.net[/email])
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/




--
RegardsKevin 

Post BackupPC on VLAN 
I agree with Les Mikesell, but if you cannot find the way to resolve this in the correct way, you can patch it adding the routes manually in you backup server. It not the best way, but should work
Regards

On Tue, Jan 17, 2012 at 3:38 AM, Les Mikesell <lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])> wrote:
On Tue, Jan 17, 2012 at 12:11 AM, Kevin Kimani <kevinkimani < at > gmail.com ([email]kevinkimani < at > gmail.com[/email])> wrote:
Hi guys,

I have setup backuppc running on Centos5.7. I have a vlan setup with
different subnets. Am trying  to resolve the computer names by name hence
using nmblookup. Am only able to resolve the machine on the same subnet as
the backup server. I can ping machines on the other subnets but when I try
to resolve their names, am unable. Then I decided to add virtual networks to
the backup server of the subnets. Upon doing this, was unable to reach the
other networks.

Could you help PLEASE.



The best approach is to set up DNS with either static IPs or a system
that lets the DHCP-assigned machines register their addresses
dynamically.   Next best is a central WINS server (the DHCP server
gives out it's address and you can use samba on the backuppc server if
you don't have another suitable machine).

But, if you have connected a VLAN trunk to the backuppc server and
given it an interface and address on each of the relevant VLANS,
nmblookup should be able to find everything with broadcasts.   I don't
understand your problem with other networks, but it is probably simple
routing.  Be sure the netmask is correct for each interface and that
you have only assigned one default gateway (i.e. the new VLAN
interfaces should probably not have a GATEWAY entry).

--
 Les Mikesell
   lesmikesell < at > gmail.com ([email]lesmikesell < at > gmail.com[/email])

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net ([email]BackupPC-users < at > lists.sourceforge.net[/email])
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/


Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB