RE: VISTA issues with Netserver -- MIDRANGE-L

This seems rather interesting. I'm sorry, i can't offer you a solution.

Are you current on your i5/OS release? As i said, we're running V5R4
with newest PTFs, and it is (without browsing) working flawlessly.

I would suggest you to use Wireshark (http://www.wireshark.org) to
capture the traffic with your system. Then have a look at the Samba
Documentation in order to understand the SMB/CIFS traffic you're seeing.

You should also open a PMR with ibm
(https://www14.software.ibm.com/webapp/set2/ssr/probsearch)

Hope this helps a little bit,

Lukas

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chad Carroll
Sent: Friday, February 23, 2007 4:29 PM
To: Midrange Systems Technical Discussion
Subject: RE: VISTA issues with Netserver

Lukas, 

Using gpedit I found the setting you mentioned. They
are the same settings you can access by runing
secpol.msc.

So I found the following settings below relating to
what you are talking about. How are you saying they
need to be set to work properly with the netshare? 

I set them all to enabled, then ran gpupdate and
tried, it did not work. I switched them all to
disabled and ran gpupdate, and still no change. I then
put them all at the windows default, still no change. 

Thank you for the help.

Domain member: Digitally encrypt or sign secure
channel data (always)
Domain member: Digitally encrypt secure channel data
(when possible)
Domain member: Digitally sign secure channel data
(when possible)

Microsoft network client: Digitally sign
communications (always)
Microsoft network client: Digitally sign
communications (if server agrees)

Microsoft network server: Digitally sign
communications (always)
Microsoft network server: Digitally sign
communications (if client agrees)


--- Lukas Beeler <l.beeler@xxxxxxxxxxx> wrote:

You should use gpedit.msc, not the group policy
managment console.

Every machines has a local set of group policies,
which you might want
to edit, or at least look at to find a possible
culprit. Most of windows
intrinsic details can be changed using group
policies - this also holds
true for non-domain machines.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Chad Carroll
Sent: Thursday, February 22, 2007 11:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: VISTA issues with Netserver

Lukas,

Thank you for the response. I am not running a
domain
on this network, and I am not joining a domain with
this vista computer. It is just a simple 10 node
workgroup behind our 9406-270.

If I try to run the Group Policy Managemnt I receive
the "To manage Group Policy, you must log on to the
computer using a domain user account"

Is it possible that not joining a domain will
prevent
this from working properly with Vista?

Thanks again,
Chad

--- Lukas Beeler <l.beeler@xxxxxxxxxxx> wrote:

Hi Chad,

Your problem is called "SMB signing". Windows

Vista

required this by
default, when joined into a Domain. If not, you

have

different problem,
our the computers you got shipped differ from
microsofts default. 

I'm using Vista Business on my Laptop as i type
this, and i'm able to
access shares on our 9406-270, running V5R4 at 

C7002540

HIPER 34
TCP/IP 4

Im not able to browse shares though. My Laptop is
joined to a Windows
2003 Domain, with default policies applied.

I can access \\machine\PDF\
But i can't access \\machine\ (i get "Permission
denied"). 

Here's how you solve the SMB signing problem:

Type "gpmc.msc" into the search field.

Answer YES tot he UAC prompt

Now, this is translated from German, so it might

not

be identical to
what yo usee.

Click on

Computer Configuration

Windows Configuration

Security Settings

Local Policies

Security Options

Look for "Sign communication digitally"

It should be in Microsoft's Network Client and
Domain Client groups.

Change them, then run gpupdate.

-----Original Message-----
From:

midrange-l-bounces+l.beeler=dataline.ch@xxxxxxxxxxxx

[mailto:midrange-l-bounces+l.beeler=dataline.ch@xxxxxxxxxxxx]

On Behalf
Of Chad Carroll
Sent: Thursday, February 22, 2007 10:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: VISTA issues with Netserver

Chris,

Thank you for the response. The password level was
indeed at 0. I changed it to 2 then restarted
netserver. 2000 pro and XP pro are still

connecting

without issue, however Vista is still experiencing
the
same problems. 

 
--- Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>

wrote:

I believe you need to set your password level to
either 1 or 2 which
disables support for Win98.  But this is a

guess.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On

Behalf

Of Chad Carroll
Sent: Thursday, February 22, 2007 11:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: VISTA issues with netserver

Hello,

I posted this on PCTECH the other day but have

not

received any
response. I noticed some decent vista

discussions

on

this list so
figured I would post here.

I was wondering/hoping if any of you that have
played with Vista so far
have had any problems or specific workarounds in
order to get Vista to
map to any of your netserver shares? I know of

the

issues with
operations console and other Client Access

issues,

but I have not seen
anything that made me think that mapping to a

share

would be such an
issue. Did I miss something extremely obvious? I
guess it wouldn't be
the first time.

We have multiple shares on our internal iSeries

that

I can not get 3
brand new Dell boxes running Vista Buisness to
connect to. I have looked
and search through countless forums and articles

and

can not come up
with a solution. 

The shared drive is on an v5r1 box. The vista

boxes

all have Client
Access v5r4 with the latest apar installed on

them.

This server is also
our DNS, DHCP, and lotus server for this

internal

network. The vista
machines all quickly picked up IP's from the

DHCP

right out of the box
and were on the internet with no issues. the
server's name is "MMI" and
I can ping, ftp, connect to mail, and connect
through our Client Access
emulator using "MMI" as an address with no

issues,

so I know the dns is
working fine. We run a Lotus Domino server on

the

=== message truncated ===




 
________________________________________________________________________
____________
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091