Still trying to get Linux/SAMBA connectivity

Large, heterogeneous network with Win98SE, WinME, Win2K, WinXP, Linux and
SGI's IRIX. I'm stuck trying to get SAMBA connectivity between the Linux
box and two computers that have Norton AV 2005, Win2K and WinXP boxes.

I'm pretty sure that the problem is NAV2005 because I can connect just fine:
from Linux to a WinXP- SP2 computer with MacAfee running on it
from Linux to a Win98SE computer with NAV 2003
from Linux to a WinME computer

I'm also pretty sure that I had Linux connectivity to the Win2K and WinXP
systems that now have Norton 2005 when they had NAV 2003 too.

I've tried to enable access under the category of worm protection from my
network's address range to every port with every protocol I could find and
that doesn't help. I've tried temporarily disabling autoprotect and/or worm
protection and that didn't work either. [In all of the rules, I've either
allowed "any" port or just ports 135, 137, 138, 139, and 445 as previously
suggested.]

As a last resort, I'd like to try to disconnect from the internet and
completely disable NAV2005, but I don't know how to do that. I'd appreciate
any hints or suggestions.

I'd also appreciate help with NAV configuration -- is there something beyond
autoprotect and worm protection that I could try temporarily disabling to
figure out what the problem might be.

TIA
Norm

In article <r3tpd.58964$(E-Mail Removed)>,
"Norm Dresner" <(E-Mail Removed)> wrote:

: Large, heterogeneous network with Win98SE, WinME, Win2K, WinXP, Linux and
: SGI's IRIX. I'm stuck trying to get SAMBA connectivity between the Linux
: box and two computers that have Norton AV 2005, Win2K and WinXP boxes.
:
: I'm pretty sure that the problem is NAV2005 because I can connect just fine:
: from Linux to a WinXP- SP2 computer with MacAfee running on it
: from Linux to a Win98SE computer with NAV 2003
: from Linux to a WinME computer
:
: I'm also pretty sure that I had Linux connectivity to the Win2K and WinXP
: systems that now have Norton 2005 when they had NAV 2003 too.
:
: I've tried to enable access under the category of worm protection from my
: network's address range to every port with every protocol I could find and
: that doesn't help. I've tried temporarily disabling autoprotect and/or worm
: protection and that didn't work either. [In all of the rules, I've either
: allowed "any" port or just ports 135, 137, 138, 139, and 445 as previously
: suggested.]
:
: As a last resort, I'd like to try to disconnect from the internet and
: completely disable NAV2005, but I don't know how to do that. I'd appreciate
: any hints or suggestions.
:
: I'd also appreciate help with NAV configuration -- is there something beyond
: autoprotect and worm protection that I could try temporarily disabling to
: figure out what the problem might be.

First off: Norton sucks ass. Get rid of it.

If that's not an option, you might check if increasing the IRPStackSize
parameter helps your connectivity problem.

MS has a KB entry that describes the problem with NAV and the IRPStackSize
Parameter:

http://support.microsoft.com/default...b;en-us;177078


Cheers - Tony 'Nicoya' Mantler

--
Tony 'Nicoya' Mantler -- Master of Code-fu -- (E-Mail Removed)
-- http://nicoya.feline.pp.se/ -- http://www.ubb.ca/ --

"Norm Dresner" <(E-Mail Removed)> wrote in message news:<r3tpd.58964$(E-Mail Removed)>...
> Large, heterogeneous network with Win98SE, WinME, Win2K, WinXP, Linux and
> SGI's IRIX. I'm stuck trying to get SAMBA connectivity between the Linux
> box and two computers that have Norton AV 2005, Win2K and WinXP boxes.
>
> I'm pretty sure that the problem is NAV2005 because I can connect just fine:
> from Linux to a WinXP- SP2 computer with MacAfee running on it
> from Linux to a Win98SE computer with NAV 2003
> from Linux to a WinME computer
>
> I'm also pretty sure that I had Linux connectivity to the Win2K and WinXP
> systems that now have Norton 2005 when they had NAV 2003 too.
>
> I've tried to enable access under the category of worm protection from my
> network's address range to every port with every protocol I could find and
> that doesn't help. I've tried temporarily disabling autoprotect and/or worm
> protection and that didn't work either. [In all of the rules, I've either
> allowed "any" port or just ports 135, 137, 138, 139, and 445 as previously
> suggested.]
>
> As a last resort, I'd like to try to disconnect from the internet and
> completely disable NAV2005, but I don't know how to do that. I'd appreciate
> any hints or suggestions.
>
> I'd also appreciate help with NAV configuration -- is there something beyond
> autoprotect and worm protection that I could try temporarily disabling to
> figure out what the problem might be.
>
> TIA
> Norm

Hi Norm,

I would disconnect from the Internet and completely uninstall NAV,
then try and establish a samba connection. If so, you defintely know
that your problem lies with NAV. Try using a packet sniffer such as
ethereal on your linux box to establish which ports samba is using to
connect. This will give you a good place to start. You aren't
running a firewall on the winXP box are you?

Hope this helps.

Ben.

"Ben Halicki" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Norm Dresner" <(E-Mail Removed)> wrote in message
news:<r3tpd.58964$(E-Mail Removed)>...
> > Large, heterogeneous network with Win98SE, WinME, Win2K, WinXP, Linux
and
> > SGI's IRIX. I'm stuck trying to get SAMBA connectivity between the
Linux
> > box and two computers that have Norton AV 2005, Win2K and WinXP boxes.
> >
> > I'm pretty sure that the problem is NAV2005 because I can connect just
fine:
> > from Linux to a WinXP- SP2 computer with MacAfee running on it
> > from Linux to a Win98SE computer with NAV 2003
> > from Linux to a WinME computer
> >
> > I'm also pretty sure that I had Linux connectivity to the Win2K and
WinXP
> > systems that now have Norton 2005 when they had NAV 2003 too.
> >
> > I've tried to enable access under the category of worm protection from
my
> > network's address range to every port with every protocol I could find
and
> > that doesn't help. I've tried temporarily disabling autoprotect and/or
worm
> > protection and that didn't work either. [In all of the rules, I've
either
> > allowed "any" port or just ports 135, 137, 138, 139, and 445 as
previously
> > suggested.]
> >
> > As a last resort, I'd like to try to disconnect from the internet and
> > completely disable NAV2005, but I don't know how to do that. I'd
appreciate
> > any hints or suggestions.
> >
> > I'd also appreciate help with NAV configuration -- is there something
beyond
> > autoprotect and worm protection that I could try temporarily disabling
to
> > figure out what the problem might be.
> >
> > TIA
> > Norm
>
> Hi Norm,
>
> I would disconnect from the Internet and completely uninstall NAV,
> then try and establish a samba connection. If so, you defintely know
> that your problem lies with NAV. Try using a packet sniffer such as
> ethereal on your linux box to establish which ports samba is using to
> connect. This will give you a good place to start. You aren't
> running a firewall on the winXP box are you?
>
> Hope this helps.
>
> Ben.

No, no Firewall -- at least not that I know -- and definitely not on the
Win2K box. I'm certain that I had connectivity before I installed NAV so
I'll probably give uninstalling it a try. Thanks for the suggestion.
Norm

It was, after all is said and done, my fault. It always is!

At least this time Norton AntiVirus was "blameless".

I have for about a decade, used a set of environment variables to represent
filenames so I can reference them on command-lines without even thinking
about where they are or what they're called in various OS. [Just about all
*NIX OS have identical file structures for system files but there are
variant OS that I use too.]

One of these environment variables is a shorthand for the password file,
PASSWD so I can type
edit $PASSWD
on just about any OS I use and get the right file into the editor. At least
the version of SAMBA included in RedHat 7.2 uses that environment variable
in te program `smbclient` to be an override for the password to use in
making the connection. Whoops! My fault! Definitely, no argument. But I
have to wonder why this has changed since I've used this environment
variable in SGI's IRIX since 5.2 and in Linux since RedHat 5.1 with no ill
effects. Progress. Bah!

Thanks to all who tried to help.

Norm

Glad to hear you have resolution Norm.

Dave




"Norm Dresner" <(E-Mail Removed)> wrote in message
news:PQHpd.979076$(E-Mail Removed)...
| It was, after all is said and done, my fault. It always is!
|
| At least this time Norton AntiVirus was "blameless".
|
| I have for about a decade, used a set of environment variables to represent
| filenames so I can reference them on command-lines without even thinking
| about where they are or what they're called in various OS. [Just about all
| *NIX OS have identical file structures for system files but there are
| variant OS that I use too.]
|
| One of these environment variables is a shorthand for the password file,
| PASSWD so I can type
| edit $PASSWD
| on just about any OS I use and get the right file into the editor. At least
| the version of SAMBA included in RedHat 7.2 uses that environment variable
| in te program `smbclient` to be an override for the password to use in
| making the connection. Whoops! My fault! Definitely, no argument. But I
| have to wonder why this has changed since I've used this environment
| variable in SGI's IRIX since 5.2 and in Linux since RedHat 5.1 with no ill
| effects. Progress. Bah!
|
| Thanks to all who tried to help.
|
| Norm
|
|