Vista crashes WSeB

[Tony S]

We've been running WSeB for years in our dept. Then we had test to run
with Vista which
resulted in WSeB trapping.

Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?

The user never gets connected or authenticated.

One sorry about Vista even though it was not able to connect to it it
keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the server
Traps again.
The only to stop it is to get the Vista machine off the net.

Any others seen this?
--
Tony,

*******************************************
Tony Saucedo
SIEMENS ITS
Austin, Texas
To reply or email remove "_nospam"
*******************************************


[Chuck McKinnis]

On Fri, 9 Mar 2007 05:02:34 UTC, Tony S <TonyS-at-ITS-Siemens-dot-com>

Post by Tony S
We've been running WSeB for years in our dept. Then we had test to run
with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to it it
keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the server
Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with the
rest of the world.

[Tony S]

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S <TonyS-at-ITS-Siemens-dot-com>

Post by Tony S
We've been running WSeB for years in our dept. Then we had test to run
with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to it it
keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the server
Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with the
rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

[William L. Hartzell]

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S <TonyS-at-ITS-Siemens-dot-com>

Post by Tony S
We've been running WSeB for years in our dept. Then we had test to
run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to it it
keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with the
rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings for
Vista' behavior with respect to SMB version 2.x, which is what OS/2
uses? Microsoft surly has a help article on how to configure the
compatibility mode.

[David]

Post by William L. Hartzell

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S

Post by Tony S
We've been running WSeB for years in our dept. Then we had test to
run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to it
it keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with the
rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings for
Vista' behavior with respect to SMB version 2.x, which is what OS/2
uses? Microsoft surly has a help article on how to configure the
compatibility mode.

I have had same problem - do not run teh browser service under wseb. I
still cannot connect vista client to wseb network share - vista sees teh
wseb computer but won't access shares - access denied etc - it asks for
a password but does not connect. I have tried all of the settings in
teh registry - eg lanmanager compatability (NTLM etc) but to no avail.

David

[William L. Hartzell]

Post by David

Post by William L. Hartzell

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S

Post by Tony S
We've been running WSeB for years in our dept. Then we had test to
run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when a
Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to it
it keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with the
rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings for
Vista' behavior with respect to SMB version 2.x, which is what OS/2
uses? Microsoft surly has a help article on how to configure the
compatibility mode.

I have had same problem - do not run teh browser service under wseb. I
still cannot connect vista client to wseb network share - vista sees teh
wseb computer but won't access shares - access denied etc - it asks for
a password but does not connect. I have tried all of the settings in
teh registry - eg lanmanager compatability (NTLM etc) but to no avail.

I'd make a bitch with Microsoft and wait for service pack one. Put XP
back on that machine in the mean time.

[Bruce D]

Post by William L. Hartzell

Post by David

Post by William L. Hartzell

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S

Post by Tony S
We've been running WSeB for years in our dept. Then we had test
to run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when
a Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to
it it keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with
the rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings
for Vista' behavior with respect to SMB version 2.x, which is what
OS/2 uses? Microsoft surly has a help article on how to configure
the compatibility mode.

I have had same problem - do not run teh browser service under wseb.
I still cannot connect vista client to wseb network share - vista
sees teh wseb computer but won't access shares - access denied etc -
it asks for a password but does not connect. I have tried all of the
settings in teh registry - eg lanmanager compatability (NTLM etc) but
to no avail.

I'd make a bitch with Microsoft and wait for service pack one. Put XP
back on that machine in the mean time.

I have had customers bring in their Sony VAIO VGN-SZ48G laptops to me
asking to have Vist taken off and replaced back with XP. Vista will not
work in their Windows NT domains. Can't connect to shares they say.

My 2 cents worth

[David]

Post by Bruce D

Post by William L. Hartzell

Post by David

Post by William L. Hartzell

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S

Post by Tony S
We've been running WSeB for years in our dept. Then we had test
to run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when
a Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to
it it keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with
the rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings
for Vista' behavior with respect to SMB version 2.x, which is what
OS/2 uses? Microsoft surly has a help article on how to configure
the compatibility mode.

I have had same problem - do not run teh browser service under wseb.
I still cannot connect vista client to wseb network share - vista
sees teh wseb computer but won't access shares - access denied etc -
it asks for a password but does not connect. I have tried all of the
settings in teh registry - eg lanmanager compatability (NTLM etc) but
to no avail.

I'd make a bitch with Microsoft and wait for service pack one. Put XP
back on that machine in the mean time.

I have had customers bring in their Sony VAIO VGN-SZ48G laptops to me
asking to have Vist taken off and replaced back with XP. Vista will not
work in their Windows NT domains. Can't connect to shares they say.
My 2 cents worth

While I cannot connect vista to my wseb server box, i can connect vista
to an ecs box. perhaps vista is not compatible with the older
networking software on wseb but not ecs 2.0?

david

[David]

Post by David

Post by Bruce D

Post by William L. Hartzell

Post by David

Post by William L. Hartzell

Post by Tony S

Post by Chuck McKinnis
On Fri, 9 Mar 2007 05:02:34 UTC, Tony S

Post by Tony S
We've been running WSeB for years in our dept. Then we had test
to run with Vista which
resulted in WSeB trapping.
Has anyone experienced Trap E on Warp Server for e-Business when
a Windoze Vista
pc tries to connect to it?
The user never gets connected or authenticated.
One sorry about Vista even though it was not able to connect to
it it keeps trying even after
a reboot, because no matter if the Vista machine is rebooted the
server Traps again.
The only to stop it is to get the Vista machine off the net.
Any others seen this?

Why am I not suprised? I suspect that the superior programmers at
Microsoft did not worry about maintaining any compatibility with
the rest of the world.

I know another Microshaft incompatibility issue.
Just wondering if anyone had hit the same problem.
Thanks.

I'd make a WAG but did you look into the
what-the-hell-do-they-call-the-registry now days, for the settings
for Vista' behavior with respect to SMB version 2.x, which is what
OS/2 uses? Microsoft surly has a help article on how to configure
the compatibility mode.

I have had same problem - do not run teh browser service under wseb.
I still cannot connect vista client to wseb network share - vista
sees teh wseb computer but won't access shares - access denied etc -
it asks for a password but does not connect. I have tried all of the
settings in teh registry - eg lanmanager compatability (NTLM etc) but
to no avail.

I'd make a bitch with Microsoft and wait for service pack one. Put XP
back on that machine in the mean time.

I have had customers bring in their Sony VAIO VGN-SZ48G laptops to me
asking to have Vist taken off and replaced back with XP. Vista will
not work in their Windows NT domains. Can't connect to shares they say.
My 2 cents worth

While I cannot connect vista to my wseb server box, i can connect vista
to an ecs box. perhaps vista is not compatible with the older
networking software on wseb but not ecs 2.0?
david

I finally connected my vista box to wseb for printing purposes by
enabling lpr on the wseb box and connecting vista via lpr.

To share data i use FTP.

\regards


David