Re: IDS10 on Vista
Bill,
We have seen the same problem with dbaccess in the Vista compatibility labs, however switching the firewall off did not appear to make any difference.
The workaround in our case was to run dbaccess from a command Window executed with the "Run as Administrator" option.
Microsoft engineers are currently looking at this problem, I will update.
Regards
Guy
----- Original Message ----
From: Bill Hamilton <garage_dba@hotmail.com>
To: Guy . <gbowerman@yahoo.com>; informix-list@iiug.org
Sent: Friday, March 9, 2007 1:28:07 PM
Subject: RE: IDS10 on Vista
P
{
margin:0px;
padding:0px;}
body
{
FONT-SIZE:10pt;
FONT-FAMILY:Tahoma;}
I did a netstat with firewall off and no dbaccess running.
Then started dbaccess and did netstat again.
These are the new lines that show up:
TCP [fe80::911c:68b3:6cfb:7146%8]:1526 SixForeV:49836 ESTABLISHED
TCP [fe80::911c:68b3:6cfb:7146%8]:49835 SixForeV:turbo TIME_WAIT
TCP [fe80::911c:68b3:6cfb:7146%8]:49836 SixForeV:turbo ESTABLISHED
I'll try opening 49835 and 49836.
Date: Fri, 9 Mar 2007 11:22:52 -0800
From: gbowerman@yahoo.com
Subject: Re: IDS10 on Vista
To: garage_dba@hotmail.com; informix-list@iiug.org
.ExternalClass DIV
{}
It is working fine on a Vista lab machine here. I didn't set up the Firewall myself but the default Windows firewall has the following exceptions:
Core Networking
File and Printer Sharing
File Transfer Program
Network Discovery
Remote Assistance
Remote Desktop
Under Advanced, Local Area Connection is checked.
There do not appear to be any specific settings/exceptions for Informix programs.
Guy
----- Original Message ----
From: Bill64bits <garage_dba@hotmail.com>
To: Guy . <gbowerman@yahoo.com>; informix-list@iiug.org
Sent: Tuesday, March 6, 2007 7:41:19 PM
Subject: Re: IDS10 on Vista
.ExternalClass DIV
{}
I just noticed the firewall was off,
though I could have sworn I turned it back on.
I turned if on.
I tried dbaccess - no go.
Turned the firewall back off - dbaccess
works again.
I have dbaccess as an exception, so I
don't know what is stopping it from running.
----- Original Message -----
From:
Guy .
To: Bill Hamilton ; informix-list@iiug.org
Sent: Tuesday, March 06, 2007 4:07
PM
Subject: Re: IDS10 on Vista
>
Then I noticed that I had put 192.168.0.1 in the hostname in setnet32 when I
was getting desperate the other day
ah, that'd do it.
If you do
notice any problems with IDS on Vista, whether they be show-stoppers or minor
cosmetic issues please let me know, I'd like to compile a list of any
incompatibilities and start investigating.
Thanks
Guy
-----
Original Message ----
From: Bill Hamilton <garage_dba@hotmail.com>
To: Guy
Bowerman <gbowerman@yahoo.com>; informix-list@iiug.org
Sent: Tuesday,
March 6, 2007 8:38:05 AM
Subject: RE: IDS10 on Vista
.ExternalClass P
{padding:0px;}
.ExternalClass
{font-size:10pt;font-family:Tahoma;}
Thanks, Guy.
I did as you said, but IDS would
not start.
I got
09:18:36 listener-thread: err =
-25573: oserr = 0: errstr = : Network driver cannot accept a connection on the
port.
over and over and ....
I uninstalled client sdk 3.0 and
reinstalled into the C:\\program files\\IBM\\Informix
(without the default
Client SDK 3.0 on the end of the path that the installer wanted).
I had
trouble with that on win2k while testing the ifx .net provider.
I think the
informixdir gets screwed if you let it install someplace else.
The
installer did not copy data1.cab to the work directory from the zip and
aborted.
After I manually copied the .cab to the work directory it had
chosen, the install worked ok.
Then, I put back the protocol to onsoctcp
but still no-go.
Then I noticed that I had put 192.168.0.1 in the hostname
in setnet32 when I was getting desperate the other day.
I put it back to
the my computer name (which resolves to fe80::911c:68b3:6cfb:7146%8) and
IDS started.
Then dbaccess worked. It even works with the firewall
on.
> From: gbowerman@yahoo.com
> Subject: Re: IDS10 on Vista
>
Date: Tue, 6 Mar 2007 00:41:03 +0000
> To:
informix-list@iiug.org
>
> It sounds a bit firewally (if that's
an adjective) to me too. One thing
> you could try is changing the
connection protocol from onsoctcp to
> onipcnmp in the registry and
re-starting IDS:
>
> - Comment out NETTYPE in the onconfig
file
> - Change HKEY_LOCAL_MACHINE\\Software\\Informix\\SQLHOSTS\\protocol
value to
> onipcnmp
> - restart IDS
>
> If it works
it means it's just a problem with the TCP socket..
>
>
Guy
>
> Bill Hamilton wrote:
> > I tried it with
firewall off.
> > And I did the setup in setnet32.
> > I
checked the hosts file and it had nothing.
> > The services file
has
> > turbo 1526/tcp
> >
> > That look
ok?
> >
> >
> >
> >
> >
------------------------------------------------------------------------
>
> Subject: RE: IDS10 on Vista
> > Date: Mon, 5 Mar 2007 08:10:50
-0600
> > From: eemills@nationalbeef.com
> > To:
informix-list@iiug.org
> >
> > Bill-
> >
>
> Try turning the firewall completely off and see if it is
> >
eating your dbaccess connection. If it works you will need to tweak
>
> the firewall some more.
> >
> > Im assuming you
already added the port to
> > \\windows\\system32\\drivers\\etc\\services
and defined your server in
> > setnet32.
> >
> >
> >
> > --EEM
> >
> >
> >
> >
------------------------------------------------------------------------
>
>
> > *From:* informix-list-bounces@iiug.org
> >
[mailto:informix-list-bounces@iiug.org] *On Behalf Of *Bill64bits
> >
*Sent:* Sunday, March 04, 2007 6:04 PM
> > *To:*
informix-list@iiug.org
> > *Subject:* IDS10 on Vista
> >
> >
> >
> > I installed IDS10.0.TC5I1 on Vista
Business and finally got oninit
> > to run after changing the
Informix account to run as an
> > administrator and putting oninit
into the windows firewall as an
> > exception.
> >
>
> After setting my env vars, I can run onstat, etc, but dbaccess
just
> > hangs if I try to connect.
> >
> > The
last entry in the informix log is the normal "online mode" message.
>
>
> > The windows eventlog shows checkpoints are
happening.
> >
> > The service looks happy, so why can I
not connect via dbaccess?
> >
> > ODBC connections fail
also (as expected).
> >
> >
> >
> > I
turned off UAC with no affect.
> >
> > I checked local
security policy for the following on user in