Eduardo Orea wrote:
>
> On the other message you wrote actually there's a great diff in the
> networking between XP-Home and XP-Pro but neved had problems with that
> before, and that make me think a little bit more on that, and perhaps the
> problem could be also associated with it or with Windows Firewall
> (introduced on SP2) or any other firewall like Norton's.
The networking difference is one of the few diffs between XP Pro
and Home. But, the actual difference isn't that big. In fact,
I saw somewhere that someone had analyzed the contents of both
the Home and Pro installation CDs (a long time ago, even before
SP1) and found only one file different that was related to the
lack of domain logon support in XP Home.
I was also thinking more about it, and not being able to connect
to a domain is something that is at a pretty high level in the
file and printer sharing code (i.e., what Samba does). I don't
see any reason at all for this to be related to the "cannot connect
to target" problem, which would I, er, assume(?) be only related
to the low-level TCP/IP stack (that is, basic socket connections
and packet transport.). The two issues would seem to be very far
removed from each other, conceptually at least.
(But then, as far as the actual implementation of Windows networking,
who knows. :-)
> The best test enviroment could be a fresh install of XP SP1, either home or
> pro, no internet access, and just istall PODS, if it works then we have not
> an OS issue. Then start installing other things and see when it fails, yes
> it is "try and fail", but may be a good aproach, this way you can provide us
> more specific info about what's going bad, and posibly we could help you
> better.
That seems like a good idea. Divide and conquer! (Although my
.signature this time seems to suggest otherwise. :-)
Jay Ts
--
There are a lot of problems solved by doing nothing about them.
- Alan Watts
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
