Re: AS 4.1 reliability issues

Ok, I have fixed it. It was the simplest of things to fix and I have been
stuck and frustrated on this for weeks. From my Network Connections, I went
to the properties of the mobile device and I noticed that there wasn't an IP
address for it. TCP/IP was not checked. I checked that, it then got an IP
assigned and lo and behold, ActiveSync detected the device, connected and
synchronised straight away.

Even though you didn't fix it, you mentioned something which made me go look
for something else. Thanks!!!!


"Carl Wolz [MSFT]" <carlw@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:esPrx9WSGHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
Do you have "Don't allow excemptions" checked in the Windows firewall? Is
the DHCP client service running?

How far do you get in the connection process? Can you ping the device?

--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no
rights.

"Paul Murray" <p.murray@xxxxxxxxxxxxx> wrote in message
news:%23UmnGSIRGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
I have no faith in this piece of software. I have not been able to get it
to connect on either of my two computers that have .NET 2005 on. I have
been unable to install AS4.0 afterwards and get that to communicate with
my WM5 device. I have added all the ports in the MS firewall which I
don't really think is the issue. I booted up an old PC (very basic) that
has XP on and also has MS firewall active. I installed AS4.0, attached
the device and it communicated. I then upgraded to 4.1 using the latest
setup.exe on MS site. After a reboot, it was able to recognise the
device. Wow, AS4.1 talks for the first time to my PDA. Great
achievement. I did not have to fiddle with the MS firewall at all. So I
upgraded my main PC which still had 4.0 and the one I use to keep my PDA
current. After a reboot, it did not recognise the device. What gives?





.

Relevant Pages

  • RE: red hat firewall question
    ... Well I've already determined that this will fix the issues. ... if I can get the firewall to do it's own version of "ping" using "keep ... state" then it will take affect for all tcp connections to the server. ...
    (RedHat)
  • Re: What is the Pattern here ?
    ... These are all Dialup Connections that I had no connection with at the time. ... It's obviously an enormous security hole, ... > and a real firewall box. ...
    (comp.security.firewalls)
  • Re: Black Ice confesses faulty program!!!
    ... > outgoing connections or traffic except in cases where these connections ... > "dangerous/suspicious" traffic by the BlackICE program. ... > get into your machine then even a PC *without* a firewall is completely ... If you don't think "Spyware" is a problem for computer ...
    (comp.security.firewalls)
  • Re: Port 135
    ... The patch doesn't disable DCOM / RPC, so connections can still be made. ... That's why you need a firewall. ... the patch is not the thing to control ... control over your TCP/IP ports and services, ...
    (microsoft.public.security)
  • Re: Networking/Security Question...
    ... The router itself will be a Cisco 1721. ... >setup is very simple... ... XP sp2 having the firewall on by default. ... > # but deny established connections that don't have a dynamic rule. ...
    (freebsd-net)
Loading