Re: CE 6.0 Networking Problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes, it is 254. That is what my host PC also has for subnet mask. I've been
told by our Network admin that is correct as well and is controlled by the
DHCP server.

--
Thanks,

George


"Paul G. Tobey [eMVP]" wrote:

Double-check: 254? in 255.255.254.0?

Paul T.

"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:467E9A92-CA25-46E4-B329-8F25EC26ECD2@xxxxxxxxxxxxxxxx
Paul,

Thanks again for the reply.

Yes, the subnet masks are the same, 255.255.254.0.

I was afraid you were going to say something might be wrong with the
driver.
This is a 3rd party driver from SMSC so it's probably some configuration.
I
will have a look again and see if I can find anything I may have missed
before.

I will also try a debug build and see if I get any new information.

I'll post anything new I find.

--
Thanks,

George


"Paul G. Tobey [eMVP]" wrote:

Just for quick grins, make sure that there is no firewall running on your
PC. As you say, the address appears fine, as long as the subnet masks on
each device are correct; I would guess 255.255.255.0.

The most-likely cause that I can think of is a problem with the Ethernet
driver. It could be that interrupts aren't working right for some reason
(you've got them configured for 'edge' sensitivity, but the controller
doesn't work that way, etc.) It could also be a problem with the
registry
settings for the driver (maybe the register stride is something other
than
1, but you haven't set a registry option that tells the driver that). I
would expect these basic sorts of things to be weeded out by being able
to
ping outward to the PC, though. The next thing would be to build a debug
image, with the full debug messages, and see what the messages from the
driver, and the system, might tell you about what's going on.

Paul T.

"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE105AEE-B5CD-4AFA-916C-28A9A81734D9@xxxxxxxxxxxxxxxx
Thank you for the reply. My apologies, I failed to provide some
valuable
information.

This is a retail image running the real driver and executing out of NOR
flash, KITL is not being used.

Also, the IP address does seem valid. My development machine is
10.7.236.14
and my target gets 10.7.236.13. So to me that means it's a valid
address.

The Ethernet card I'm using is SMSC 9118 (LAN9217 family).

Hope that helps. Any other information I can provide let me know.

--
Thanks,

George


"Paul G. Tobey [eMVP]" wrote:

Is the IP address it's getting *valid*? If you're on a firewalled
network
(there's a firewall between you and the Internet), tell us your
development
PC IP address and the one that the device is getting (since they're
not
externally accessible to us anyway).

This is a debug image running VMini over KITL? Or it's a retail image
running the real driver for your Ethernet card? What type of Ethernet
card
is it?

Paul T.

"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7779CD4-4DFB-4C0B-B6E1-A570CE473C6D@xxxxxxxxxxxxxxxx
Hi,

I am having problems connecting my custom target device, running a
Freescale
i.MX31 platform with CE 6.0.

Right now I am simply trying to ping my device but am not having any
success. I'm also trying to reach the internet with the IE browser
but
that
is not working either.

It appears that my device can talk to the DHCP server correctly, as
it
obtains an IP address. And I can ping my development machine from
my
target
successfully, i.e. receive a reply. But when I ping my target from
my
development machine my target does not respond.

Also, on the IE browser on my target I see that it is connected on
the
"Local intranet" as is displayed on the bottom ride side of the
browser
pane.
So something appears to perhaps be blocking it? I do not have the
'Firewall' catalog item included in my image, so I don't think it's
the
firewall on the target unless there is some other security feature I
am
not
aware of.

Can anyone help please? What catalog items are needed in the image
to
be
able to browse the internet, ping the target, connect to it, etc.
I've
tried
to provide useful information but I can provide more. I could also
list
all
the network related items I've included in my image if that's
helpful.

--
Thanks,

George









.

Relevant Pages

  • Re: CE 6.0 Networking Problems
    ... Paul T. ... This is a 3rd party driver from SMSC so it's probably some configuration. ... and my target gets 10.7.236.13. ... Right now I am simply trying to ping my device but am not having any ...
    (microsoft.public.windowsce.embedded)
  • Re: CE 6.0 Networking Problems
    ... Paul T. ... Also, if I'm pinging from my PC, and then go to my target and ping my host ... Perhaps it's a timing issue in the driver? ...
    (microsoft.public.windowsce.embedded)
  • Re: Frequent network access freeze (in 7.0)
    ... problem with the if_tx driver. ... The usual starting diagnostics when ping fails are to try to use tcpdump to determine whether it's receive or transmit failing. ... Quiet the network between two endpoints as much as you can so you can avoid noise from making the dumps more complex, and dump arp and icmp at both endpoints. ... This would be indicative of a driver bug in which it fails to properly handle transmit queues filling, and might only trigger under very high load. ...
    (freebsd-current)
  • Re: Frequent network access freeze (in 7.0)
    ... Network access freezes very frequently. ... ping to any ip address. ... problem with the if_tx driver. ... example) transmit queues ...
    (freebsd-current)
  • Re: CE 6.0 Networking Problems
    ... make sure that there is no firewall running on your ... settings for the driver (maybe the register stride is something other than ... and my target gets 10.7.236.13. ... Right now I am simply trying to ping my device but am not having any ...
    (microsoft.public.windowsce.embedded)