> KM, I'm always amazed at how the more I learn about all of this the
> more I realize my own ignorance. Translation: this stuff makes me
> feel like a learned IDIOT.
>
> Anyway, enough self-bashing, to answer your questions:
>
> 1) I'm running SP2+FP2007 (I thought there was a problem so I
> reinstalled and ran the updates again... only to discover that I
> couldn't see most of the components because my visibility was set too
> high... geez, I wish I could afford the &$!!$*#@ classes, but it's
> just not possible)
> 2) I have NOT tried creating an XPPro emulation and didn't know that I
> could do such a thing. I've spent the past three weeks massaging this
> particular image to work with a custom shell and the propietary
> software written by our software development company (who had the
> honor of doing this job before I showed up and made the mistake of
> saying, "Sure, I can learn how to do that. No problem." My father
> was taught, in the Marine Corps, to NEVER VOLUNTEER. Guess it didn't
> pass to this generation... c'mon, laugh with me...)
> 3) The thing is, the firewall component for internet connection
> sharing (ICS) was installed but I didn't add the Control Panel
> component until just this morning.
> 4) I did add far too much, I'll admit. It stopped being precision
> surgery and turned into good old fashioned "shotgun therapy" many days
> ago. I've just been guessing (relatively educated guesses but still
> less-than-confident hail Mary passes... so to speak) and would rather
> be more aware of what the problem really is than accidentally fix it
> and not understand the how/why of it all.
>
> Here's the exact detail that I need to resolve. I'm able to create an
> incoming connection and allow the machine to automatically accept the
> incoming call, verify the login and establish the link. It all boils
> down to the transport (possibly protocol) or networking (maybe the
> same thing). I keep hearing this small voice in my head say that it's
> related to DNS, but that shouldn't matter if I manually set the IP
> addresses of both systems, right? (which I've done) So the question
> is, what will force IP over PPP and allow the systems at both ends to
> recognize each other as being on the same workgroup generated P2P
> network?
>
> Okay, another admission of ignorance (I'm learning quickly, though).
> Do I stand a better chance of doing the process of running regmon,
> filemon and/or sysdiff on the separate installations to find the
> missing link? Even though I've heard of those things, I'm new to all
> of this and have never done it. Which means, stepping up and teaching
> myself how. Which I can do.
>
> Anyway, enough rambling. I do, very sincerely, appreciate all of your
> help and input.
>
> - Jodie
>
> On Mar 16, 6:12 pm, "KM" nospam_yahoo.com> wrote:

>> I must admit Dial-up issues on XPe are always hard to investigate. The reason is that that particular part of the XPe (XPPro)
>> stack
>> has NOT been componentized in the granularity we'd want.
>>
>> Anyway, a couple of ideas and questions:
>> 1) What build you are playing with? SP1, SP2, SP2+FP2007?
>> 2) Since XP Pro shows the right results there, did you try creating XPProEmulation image for the target for testing purposes
>> to
>> see if the issue is indeed there because of a missing component(s)? (XPProEmulation image you can find onwww.xpefiles.com, highly
>> recommend only use the latest FP2007's version)
>> 3) Make sure to turn OFF the firewall on your XPe image. I don't really think this is your problem but just in case it was
>> worth
>> to mention.
>> 4) For all the networking connection you have set up on your XPe image (incoming, LAN, etc.) go to the properties and remove
>> all
>> the protocols and clients you don't really need. Often on big fat XPe image, since you might have unintentionally added some
>> components in your image like Novel client, IPX protocol and etc., you may see how many objects are linked to particular network
>> adapter that you don't need and never wanted. Remove those unnecessary protocols, clients and services and re-test.
>>
>> --
>> =========
>> Regards,
>> KM
>>
>>
>>

>>> I've reviewed the post from KM about the primary components needed to
>>> enable dial-up in XPe but, after verifying I've got every component
>>> (except Dial-Up Server Q318138, which isn't listed in my components in
>>> Target Designer but IS in the Component Designer) I'm still having a
>>> problem. When I run XP Pro on the very same machine (different HDD)
>>> I'm able to dial in to the target system and navigate the hard drive
>>> just as though I'm connected through our LAN. However, with XPe
>>> installed and RAS set up it answers the phone and establishes the
>>> connection but I can't ping the system nor see it or any of it's
>>> contents (the funny thing is it drops the LAN connection, too, until I
>>> disconnect the remote computer, flush the DNS and repair the
>>> connection). So, I'm assuming that it's not using the correct
>>> connection protocol or some other networking component that I've left
>>> out. I've tried to fix this for over a week (I wish I was
>>> exaggerating here, folks) and haven't had any success. Please let me
>>> know any suggestions or if I can provide, or even find, more
>>> information that will help. I really am at the end of my rope (the
>>> one they tie me to my desk with) and don't have anywhere else to turn.

>>

>>> Does anyone have any idea what I can do?

>>

>>> Love and light.- Hide quoted text -

>>
>> - Show quoted text -

>
>