Routing issue between two Linux servers

Hello, I have a fedora box with IP Masquerading setup. I used the instructions on tldp.org (http://tldp.org/HOWTO/IP-Masquerade-HOWTO/firewall-examples.html) to set it up. The problem is that I can't ssh from my firewall box to any internal linux box. my firewall is configured eth0 as internal and eth1 as external and just using basic iptables ruleset from the tutorial. When I try to ssh to my internal box 192.168.0.x from the external box I get " ssh: connect to host 192.168.0.x port 22: No route to host". I can ping the ip fine. My routing table looks like this:
[root@oracle rc.d]# ip route show
192.168.0.11 via 192.168.0.1 dev eth0
192.168.0.0/24 via 192.168.0.1 dev eth0
external_IP/24 dev eth1 proto kernel scope link src ISP_address
169.254.0.0/16 dev eth0 scope link
default via ISP_gateway dev eth1
[root@oracle rc.d]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.11 192.168.0.1 255.255.255.255 UGH 0 0 0 eth0
192.168.0.0 192.168.0.1 255.255.255.0 UG 0 0 0 eth0
external_IP 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 ISP_gateway 0.0.0.0 UG 0 0 0 eth1
what's wrong with my routing table? Please help.
BTW: the natting works fine, I can ssh to the firewall box on both interface fine. just can't ssh/telnet from the firewall to anywhere else.
Thanks.

what are your AD costs between A, B and C?
In Exchange 2010, each message recipient is always associated with only one Active Directory site, and there is only one least cost routing
from the source Active Directory site to the destination Active Directory site
If the least-cost routing path to the primary site contains any hub sites, the message must be
routed through the hub sites

Similar Messages

Routing issue between two satellites sites and one central hub

Hi,
I have 3 Ad sites with one exchange 2010 hub,cas,mailbox server on each sites.
One of this site (site A) is central Hub and the two other sites ( B and C) are two satellites of site A.
The is no connectivity between site B and C, only connectivity between A and B, and A and C.
When I send a mail from Site B to Site C, Exchange try to deliver the mail directly to site C and don't pass to site A to deliver to site C, some mail stay in queue in site B, and the the queue is in retry.
I flag the site A as HUB.
Site toplogy is correct and the cost too.
Can someone help me??
Thanks

what are your AD costs between A, B and C?
In Exchange 2010, each message recipient is always associated with only one Active Directory site, and there is only one least cost routing
from the source Active Directory site to the destination Active Directory site
If the least-cost routing path to the primary site contains any hub sites, the message must be
routed through the hub sites

Routing issue between Cisco Nexus and Cisco 4510 R+E Chassis

We have configured Cisco Nexus 7K9 as core and Cisco 4510 R+E as access switches for Server connectivity.
We are experiencing problem in terms of ARP learning and Ping issues between Cisco Nexus and end hosts.

Hi,
So you have N7k acting as L3 with servers connected to 4510?.
Do you see the MAC associated with failing ARP in 4510?. Is it happening with all or few servers?. Just to verify if it is connectivity issue between N7k and 4510, you can configure an SVI on 4510 and assign address from same raneg (server/core range) and perform a ping.
This will help narrow down if issue is between server to 4510 or 4510 to N7k.
Thanks,
Nagendra

How share directory between two Linux nodes?

Dears,,
I am trying to install Oracle RAC on two Linux nodes . . .
But i need to make directory shared between the both nodes
directory is /ocfs/clusterware
I need to make this directory shared between them
I mean , if create file in this directory in the first node , I must see it from the second node.
As example:
On first node:
[root@rac1 clusterware]# touch test
On second node:
[root@rac2 clusterware]# ll
Should find test file
How can i make this please?
Edited by: M o h a m m e d on Apr 29, 2010 3:44 AM
Edited by: M o h a m m e d on Apr 29, 2010 3:44 AM

Dear,,
I already followed steps located in the following link . . .
[http://www.docstoc.com/docs/4603014/Install-Oracle-RAC-10g-on-Oracle-Enterprise-Linux-Using-VMware-Server/]
and i created the following in my lap top drive J:\
J:\RAC Virtual Machine\RAC\RAC 1
J:\RAC Virtual Machine\RAC\RAC 2
and J:\RAC Virtual Machine\RAC\Shared Storage
that contain the following:
asmdisk1.vmdk , asmdisk1-flat.vmdk , asmdisk2.vmdk , asmdisk2-flat.vmdk ,
asmdisk3.vmdk , asmdisk3-flat.vmdk , ocfs2disk.vmdk , ocfs2disk-flat.vmdk
I executed the following command in RAC 1
*[root@rac1 ~]#mount -t ocfs2 -o datavolume,nointr /dev/sdb1 /ocfs*
Succeded
But in RAC 2
*[root@rac2 ~]#mount -t ocfs2 -o datavolume,nointr /dev/sdb1 /ocfs*
ocfs2_hb_ctl: OCFS2 directory corrupted while reading uuid
mount.ocfs2: Error when attempting to run /sbin/ocfs2_hb_ctl: "Operation not per mitted"
How solve this please ?

How to route traffic between two different interfaces

Hi,
I need to setup a routing between two different interfaces on a host.
Inferface ce1 : 192.168.120.12
Inteface ce2 : 192.168.110.50
Is it possible to add a route which enables the ce2 interface to catch packets from the ce1 interface ?
Regards,
Armin

The problem is a application which is only able to listen on one interface.
To fix this, I have to make all packages visible on one interface.

Linking JMS Queues between two managed servers

I have an environment setup with an AdminServer and multiple managed servers all under the same domain and on the same cluster. They are all running under the same Instance of weblogic on one Windows Server.
          I have two different applications on two managed servers that need to have a JMS Queue be linked between them. Essentially have Server1's 'inbox' link to Server2's 'outbox' and Server2's 'inbox' link to Server2's 'outbox'. Each has their own name for their inbox or outbox.
          Server1(inbox)=Server2(outbox)
          Server2(inbox)=Server1(outbox)
          I've tried using Foreign JNDI Providers, however it doesn't allow me to input two addresses (Server1 and Server2).
          Is there another function that would do the same thing?
          Thanks!

You can make use of Message Bridges between any 3th party JMS provider or SAF (store & forward) if both jms servers are weblogic servers.
          Schelstraete Bart
          [email protected]
          http://www.schelstraete.org
          http://www.linkedin.com/in/bschelst
          Edited by bschelst at 04/07/2008 1:27 PM

Ale / Idoc between two different servers

Hi All,
In my scenario i am working on two different servers in which distribution of idoc is carrying out.
(Before this i have worked on same server scenarios with different clients.)
But present scenario i am working with two diferent servers,
like,
i am having 100 client in server A (sender system) and 700 client in server B(receiver system),
i have created all the basic steps like logical systems in both systems,
Assign logical systems to clients in consecutive servers,
RFC's and ports.
while creating message type under model view in server A client 100(sender system ) i can find only 100 client's logical system name, i cannot find the 700 clients logical system name.
due to both clients are in different ip address , does we need to transfer the logical system assign ment transport request to other client.
regards,
Mohd.

Hello abdul ,
When you configure a logical system for example the same system with a different client (700) it should be configured in the source system (Client 100).
In this way when you can send the relevant IDOCs via the ALE according the model view (BD64) ,the source system (100) knows that the target is the system with the client 700 .
(There is a generic RFC in the background process : INBOUND_IDOC_PROCESS).
Sender : system_100
Receiver:system_700
Message type : MATMAS
Also in order to accept the relevant Idocs in the system with client 700,you must configure a partner profile that will contain in inbound parameters the relevant message type (MATMAS).
I hope it is more understood .
Thank you,
Boaz

Transferring data between two production servers

HI All,
I have read weblogs in transferring scenarios from Dev to Qual to Prod.
But I have a different requirement in which I have to transfer data from one production server to another production server without distrubing the first production server.
Say A and B are two production servers, I wanted to transfer data from A to B on daily basis.
Please give me some ideas on this....
Thanks
Veni

Hello,
I would suggest to use IDOC for transferring data (master \ transaction ) ... to do that you need to setup logical system (prod b) and RFC connection to connect to system prod b ...
Also distributional model need to setup for pushing the outbound idoc into RFC connection through receiver port.
Thanks
Krish

Samba problems between two linux computers

I have a laptop with arch with this smb.conf
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
wins support = no
[homes]
comment = Home Directories
browseable = yes
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Themes]
path = /home/du/Themes
available = yes
browsable = yes
public = yes
writable = yes
and another pc with ubuntu with this smb.conf
# Sample configuration file for the Samba suite for Debian GNU/Linux.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
; domain logons = yes
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
[homes]
comment = Home Directories
browseable = yes
writable = yes
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = no
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = yes
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
# The CD-ROM gets unmounted automatically after the connection to the
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[Downloads]
path = /home/Duccio/Downloads
available = yes
browseable = yes
guest ok = yes
public = yes
writable = yes
Both have static ip
The problem are 2:
1- the pc cant see eachothers with nautilus under "network" but..
2- if i type in nautilus in the address bar from the arch pc "smb://ubuntu_ip" i can see shared folders the shared folder in ubuntu pc /home/Duccio/Downloads is browseable but i cant mount folders, the message is "unable to mount location"
Another pc with ubuntu wich have dhcp is visible under nautilus network
Last edited by jacopastorius82 (2010-11-02 21:14:51)

in laptop pc with arch i have installed somewhat in gnome under System-->administration called "shared folder". Maybe this sort of software override manual configuration in /etc/samba/smb.conf?
Something like that is probably standing in ubuntu as well i suppose..
Last edited by jacopastorius82 (2010-11-03 22:13:53)

Routing issue between Cisco device and Virtual machine

Hi Guys,
We have two local subnets in a virtualized environment, subnet 1 has a VM operating as a firewall, we would like all traffic for subnet 2 to go via VM on subnet 1, this will police traffic on subnet 2 and then reroute.
The infrastructure involved comprises,
Internet Edge Switch -> ASA -> Core Switch -> IBM Flex chassis
The Internet edge switch is directly connected between the ISP routers and the Cisco ASA firewall pair (A/S). The ASA is then connected to the Core switch. Connected from the core switch is an IBM Flex chassis, via a port channel (all vlans allowed)
The local subnets in question are as follows:
Vlan 101 (10.1.1.0/24)
Vlan 102 (10.2.1.0/24)
The VM in question has two NIC cards having IP address of both subnets.
NIC 1: 10.1.1.1
NIC 2: 10.2.1.1
We would like packets destined for 10.2.1.1 to land on 10.1.1.1 IP address. At the moment traffic for each vlan routes from the outside to their respective local subnets successfully, what we are having difficulty with is directing traffic for subnet 2 via subnet 1 VM firewall.
At the moment we have tried adding a static route on the core switch but it didn’t work
ip route 10.2.0.0 255.255.255.0 10.1.1.1
I will appreciate if you could share your knowledge and guide me how to achieve this goal.
Thanks in advance :-)

Hi,
I think for this to work you need a transit vlan between the VMs and the core switch. So, if you have 2 vlans on the VM (101 and 102) you use the VM switch to route between the vlans and in order to go outside the local vlans you would use the core switch. In this scenario you would not have an SVI (layer-3) interface on the core. The only thing that core will have is the layer-2 vlans (101 and102). You would than need a static route on the core switch to point to the transit vlan on the VM side.
so, for example, if the transit vlan is vlan 110 and the ip is 192.168.1.0/24
on the core you have static routes:
ip route 10.1.1.0/24 192.168.1.2 (VM side)
ip route 10.1.2.0/24 192.168.1.2 (VM side)
You also need an SVI for vlan 110 with ip address 192.168.1.1/24 on the core.
on the VM you need a default route to point to the core (192.168.1.1).
Is this what you are trying to do?
HTH

Apache / JRUN setting up trust between two app servers

Hi,
I have two applications running on Apache web server and JRUN app server.
How can i setup a trust domain between the two jrun app servers so that the user doesnt have to enter authentication credentials in both the servers when forwarded from app server 1 to app server 2?
Thanks in advance

I researched that we can do a "fake" authentication by using cookies. Has anyone does this before? Can somebody guide me on this?

Delta issues between two DSO's

This issue has been a recurrent one over past years, so maybe someone can explain me what is happening here:
The case is always the same, i.e. I try to load a delta from one DSO into another one. Let's call them DSO1, and DSO2. More in detail, the case is as follows:
1. I get an error when loading DSO1 to DSO2, due to some characteritic value's checks that I have implemented in a start routine.
2. I delete the red request from DSO2, and manually delete the wrong entryfrom DSO1.
3. I reload (full) the deleted records into DSO1, with the corrected values. At the end I check that my data into DSO1 is correct, and that the wrong record has gone.
4. I then reload a delta from DSO1 into DSO2, but I still get the same wrong record transferred, even if the record does not exist anymore in DSO1 !!
My guess is therefore that the data for deltas is fully saved in separate tables, instead of being compared at runtime. Does anyone know if my assumption is correct...If yes, how can I find this table? Is there anything I can do to solve this issue?

The error is not very important...I have implemented a check so that a field is never transferred empty. The field is not empty anymore in the source DSO, but it still exists in the change log table...Can I do something about it?
With other words: Can I force the change log to be recreated as the difference between my two DSO's, instead as a package of changed records...?
Edited by: TTBBRR on Mar 22, 2010 1:43 PM

If i create a stunnel between two solaris servers, will the databus clustering of these two servers operate successfully across this stunneled tcp channel?

we have 2 solaris servers interconnected by a stunnel. will the clustered databus that I establish between these two servers operate successfully on the stunnelized tcp connection?

You indicated the servers didn't come up correctly. Did you run "svcs -xv" on the servers to see if any services are having problems? It is my practice to run this command after rebooting a server to make sure it came up properly and if not, to identify which services have problems which need to be addressed. If you've not done this already, I'd start there. The zones service comes up rather late in the boot process and may not be up properly if there are other problems.

3945 Router Issue between WAAS Module and IOS Firewall

I have a new 3945 router with a SM-SRE-900 module for WAAS. The 3945 also has IP inspection configured. When IP inspection and WCCP redirection running at the same time, user connections to data center were all lost. If just IP inspection or WCC Rredirection but not both, user connections were good.
I'm feeling the problem is IP inspection not WAAS aware. I tried "ip inpsect waas enable", but the command was not available. The 3945 router, SM-SRE module, and the IOS code, are all newest versions. So I was wondering if anyone has seen the similar issues and had experience of enabling WAAS through IP inspection on those new products.
Here is the configuration info:
3945 G2 ISR: IOS 15.1(1)T1;
SM-SRE-900: WAAS 4.2.3 build7;
3945 LAN interface: ip inspection in and ip wccp 61 redirect in
3945 WAN interface: ip wccp 62 redirect in
3945 SM 1/0 interface: internal connection to SM-SRE module
Between 3945 and SM-SRE module: WCCP GRE redirection and IP Forwarding return.
If you are aware of any 15.1(1)T1 bugs that may be related, please let me know too.
Thanks for any help.

Hi,
This is in general for IOS / ISR. On CCO we have a very good document for ZBFW and WAAS intigration, see below
http://www.cisco.com/en/US/docs/ios/sec_data_plane/configuration/guide/sec_zone_polcy_firew_ps10592_TSD_Products_Configuration_Guide_Chapter.html#wp1118498
If you still need to run CBAC, then recommended solution in my first post should work for you.
If the router is in the middle of TCP optamization path, then depending upon optamization product you need to configure the firewall feature like anyother firewall. for Cisco WAAS we have "ip inspect WAAS enable".
Hope this has answer your question. Thanks.
Ahsan Khan

Sharer folder issue between two directly connected PC

Dear All, I have an issue regarding folder sharing. need your help to resolve this. the scenario is
two PC's are connected directly to share a folder, to open *.mdb file of a accounting software. this problem start when I moved windows XP PC's and installed windows 7 64 bit PC's. there is no compatibility issue as I run the same software on other
locations
PC A (192.168.1.200) has that *.mdb file and PC B (192.168.1.100) has to open this file through a network.
when I configured the folder share and network setting, all done well and PC B can connect with PC A and that software work well. After two days, when we start the software at PC B, its not responding when it try's to open that database file.
while analyzing, I found out that PC B can open the share folder of PC A but when open the desired database folder explore starts not responding and need to quit it by force. I also tried to share another folder of PC A but results are same.
PC A run the software with out any problem.
It seems like network issue, so I check the cable with cable tester, found it good, than I check the connectivity by ping command, it giving me <1ms time. but still change the connectors.
the hard part is that, this share folder issue arises 3-4 days a week and 2-3 days it works well, and this is happening from last 28 days. I mean, one day we start the the PC B and use the software via network, the next day we start the PC B and we don't
able to use the software,..strange.
I also change the cable connection from cross to straight as both new PC's have gigabit Ethernet but results are same.
I already contact with software company, as per them its network issue as we can use the software on local PC (PC A) and there is no error messages popup.
please help me out in this regard.
Thanks Tanveer

Hi,
Firstly, we need to identify is this file sharing or netowrking problem. If you can access to the shared folder and modify its files which locate at PC B through PC A, it indicates file sharing works with no problem.
After that, we need to check if its networking or software itself problem when reading the .mdb file.
Put the .mdb file at PC A, then using the software open it for test. If no problem, we need to use Process Monitor to capture the access trace of the software process, we should be able to find some clues.
You can access to the link below to download Process Monitor:
https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
How to capture a Process Monitor trace:
http://blogs.msdn.com/b/dswl/archive/2010/01/10/how-to-capture-a-process-monitor-trace.aspx
Learning Example:
Using Process Monitor to Troubleshoot and Find Registry Hacks:
http://www.howtogeek.com/school/sysinternals-pro/lesson5/all/
Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Roger Lu
TechNet Community Support

Routing issue between two Linux servers

Similar Messages

Maybe you are looking for