Re: Issue when changing IP address from Static to DHCP



The format of the IP address suggests that there was no network connection
established in the first case. What's the IP address of your desktop
computer? It would have to be on the same subnet as the CE device, or there
would have to be a router between them. 192.168.x.x sounds like something
associated with Active Sync. If you're trying to share network shares
through AS, I think that's the performance problem. Clear up for us whether
you are using a network adapter, how it is configured, etc. DHCP and static
IP addressing have no effect, as long as the addresses set are valid in each
case, on file sharing performance...

Paul T.

"Michael--J" <MichaelJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:23C25953-DDAD-4FE8-8D42-075EAC95128B@xxxxxxxxxxxxxxxx
> Hi,
>
> I have a board with a PXA270 chip which has a Win CE 5.0 image loaded on
> it.
> When booting, the board is given a static IP address of 192.168.0.21 (or
> something like that). I can open up Platform Builder and use Remote
> Registry
> Editor to edit the registry (the device is connected to my dev PC via
> ActiveSync on a USB cable). I can run a client application written in c# -
> it
> basically connects to a server running on my dev PC and plays "TCP packet
> tennis" by sending an object to the server and the server echoes it, and
> then
> the client echoes it and so on...
>
> I then needed to set up file sharing on the device. I couldn't do this
> with
> the static ip for some reason, so i decided to change the it to a dhcp ip
> address. This gave it an ip of 10.10.0.xxx, a subnet mask of
> 255.255.255.0,
> and gateway 10.10.0.yyy. I was able to access the "Windows CE Remote
> Management Tool" using IE on my dev PC. I gave permission to share the
> flash
> drive and the \Windows folder. I then typed \\10.10.0.xxx on my browser
> and
> it worked but it took forever to load. When i browse the shared folders,
> they
> too take a long time to load - it's very inconvenient and not very
> feasible
> to be put out in the field. I then tried running my app - it ran but it
> didn't work as nicely as before - it kept receiving packets in segments...
> I
> then tried running the Remote Registry editor again and it wouldn't work.
> Sometimes it would load, but i could browse the main keys. Other times it
> wouldn't even load.
>
> I then decided to change the ip address back to the static version and
> everything worked fine except for file sharing. What is going on here?
> Thanks
> in advance.
>


.



Relevant Pages

  • RE: Exchange/Internet disconnecting
    ... and a old SBS2003 server that was working ok, we decided to install a new ... please check if the total network connections are ... be a network connection issue more than Exchange connection issue. ... Boot that client computer into "Safe Mode with Networking" mode to see ...
    (microsoft.public.windows.server.sbs)
  • Re: What would prevent an ISAPI extension from opening a socket on IIS 6?
    ... Both fail when they try to make that network ... way as to make opening any network connection impossible. ... > on your Windows Server 2003 but not your customer's? ... > through ISAPI Filters. ...
    (microsoft.public.inetserver.iis.security)
  • RE: Exchange/Internet disconnecting
    ... old server that I replaced had a HP5Si printer with a 3com Print server using ... please check if the total network connections are ... be a network connection issue more than Exchange connection issue. ... Boot that client computer into "Safe Mode with Networking" mode to see ...
    (microsoft.public.windows.server.sbs)
  • Re: Losing access to a shared folder
    ... that something strange with the network connection is going on. ... Both shares are on the same file server. ... domain controllers as preferred and secondary dens servers. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: new 5.1 install network problem.
    ... I believe that the DNS timeout is a symptom rather than cause ... pinging the IP address of the DNS server. ... new 5.1 install network problem. ... > the network connection worked fine, ...
    (freebsd-questions)