D3 ODBC from vmware xp?

[terr...@terrypen.com]

Just virtualized a pc that needs to connect to d3 odbc and it won't do
it. Worked fine until virtualized. Anyone run into this before?

[terr...@terrypen.com]

On Nov 19, 11:13 am, terry...@terrypen.com wrote:
> Just virtualized a pc that needs to connect to d3 odbc and it won't do
> it. Worked fine until virtualized. Anyone run into this before?

Figured it out - reloaded d3 odbc driver, re-registered dll and
recompiled vb programs that use it - all good now.
Terry

[Tony Gravagno]

terry wrote:
>Just virtualized a pc that needs to connect to d3 odbc and it won't do
>it. Worked fine until virtualized. Anyone run into this before?

Terry - Open Windows Firewall in the target and set an exclusion for
port 1603 and/or D3. That handles the server. It sounds like the
client is in vmware now, but is facing a similar port block issue. In
Windows Firewall in the client, go to Advanced, click on the primary
network adapter and click Settings. Then Add a new Service Setting
called D3ODBC for port 1603.

HTH

T

[Diets]

On Nov 19, 11:13 pm, terry...@terrypen.com wrote:

> Just virtualized a pc

Just installed Sun's VirtualBox, a new release 2.04. Small footprint,
works extremely well.

Diets

[Steven Davies-Morris]

[nods] I think so too. I run vBox on top of Ubuntu Intrepid. The
virtualized XP is great for the handful of apps I haven't yet got
around to abandoning, or have to keep around for other reasons and
won't run on top of Wine.
--
Cheers, SDM -- a 21st Century Schizoid Man
Systems Theory internet music project: <www.systemstheory.net>
on MySpace: <www.myspace.com/systemstheory>
on Last FM: <www.last.fm/music/Systems+Theory>
get "Codetalkers" *free* at <www.mikedickson.org.uk/codetalkers>
NP: nothing