OK. The problem is solved. The problem was not with samba.
The wireless subnet is controlled by a different group of people,
and after a few experiments, I found out that all out going traffic
to port 139 is dropped. So, I was able to contact my SAMBASERVER
on port 22 (ssh) but not on 139.
Till I g
On Wed, 28 May 2003, George Kasica wrote:
> Not sure if this would apply but a while ago in a Cisco router world,
> I need the command
>
> ip helper-address A.B.C.D <= Your SAMBA/WINS Server IP Address
>
> to get he various wins boxes to be seen across the network. I put one
> in for each WINS Ser
2003 6:39 AM
To: ganapathy murali krishnan
Subject: Re: [Samba] Cross Subnet WINS?
If you want it to work the win wks must be able to resolve the name
SAMBASERVER . Unfortunateley the only way it can is through wins . So
you
need to add a dns entry to your privtate dns with a hostname
SAMBASERVER
Not sure if this would apply but a while ago in a Cisco router world,
I need the command
ip helper-address A.B.C.D <= Your SAMBA/WINS Server IP Address
to get he various wins boxes to be seen across the network. I put one
in for each WINS Server on each router and all was well.
George
>Have yo
Have you walked through the DIAGNOSIS.txt troubleshooting guide?
This is test 8, I believe.
Joel
On Tue, May 27, 2003 at 06:58:04PM -0500, ganapathy murali krishnan wrote:
>
> I have a question about WINS across subnets. I am
> *not* interested in cross subnet browsing.
>
> SAMBASERVER is my P
I have a question about WINS across subnets. I am
*not* interested in cross subnet browsing.
SAMBASERVER is my PDC as well as WINS.
I run "net view \\CLIENT" on a windows machine
A which is on the same subnet as my SAMBASERVER
and everything works fine.
If I run the same command on a windows machin
