Re: Problem signing on to AIM with Net::AOLIM


I had already verified that my AOL account can send and receive IMs by logging in and exchanging IMs with another user. I also turned off my XP firewall temporarily and tried numeric IPs instead of hostnames but no luck.

To eliminate any possible Windows issues I think I will move my testing over to a Solaris server.

Thanks for the other suggestions.  I'll give them a try.

-Rick

First test a successful connection with whatever binary
graphical interface AOL provides for AIM messages. This
is to be sure you can actually connect by typical methods.
Might be your logon or password is invalid.

Chances are your default binary version has been granted
access to the internet by XP or your personal firewall.
Verify "all" is working, first, with your AOL program.

Have you granted Perl core access to the internet?

Have you received a pop-up message asking for access?

Use a fully coded version for your module.
Use explicit port numbers for both connect and logon.
Use numerical ip addresses not domain names.
Increase your time-out to ten seconds.

Turn off your XP firewall.
Turn off any personal firewall.

Be sure your router is not port forwarding elsewhere.

I know nothing about AIM. However, if AIM requires writing
a file on your local system, it is possible you need to
grant write ability through your XP system. My presumption
is AIM writes a log file somewhere, at least a log of sent
and received messages. XP might be denying access resulting
in a lack of response, thus no logon. You may need to grant
write access for your directory and directory tree in use.
For XP this is, "allow others to modify my files" or
similar wording to grant write access.

Be cautious granting write access. If a log file is needed,
discover the name, then grant write access only for that file.
I would not allow write access for all files nor directories
where you are currently working (working directory).

Another problem, again I know nothing about this module,
might be the module is not able to perform DNS lookup
to obtain an ip address. Is this module DNS capable?
This is why I suggest ip address usage.

Be sure all firewalls are turned off for testing.
Remember to turn them back on after testing.

This might be a case when you need to use a "full code"
method as shown in "Roll Your Own" documentation. If
that works, then trim it down, a little at a time,
until it quits working.

Purl Gurl



.

Relevant Pages

  • Re: [fw-wiz] Securing a Linux Firewall
    ... If it is not setuid, and not setgid, it _can't_ grant you extra privs ... > programs the firewall needs and only put those on the jumpstart CD". ...
    (Firewall-Wizards)
  • Re: [fw-wiz] AIM
    ... > Blocking AIM is tough. ... > port-blocking they've probably blocked the ip blocks for the AIM servers. ... The only way around the ISP's firewall is to get ... policy for a reason, and exceptions to, or questions about the policy ...
    (Firewall-Wizards)
  • Re: Re: Re: Strange Problem With Networking XP
    ... |>Disable the Windows XP firewall (it only protects you one way, incoming ... |>traffic) forever and get a decent firewall. ... I can tell you have used and like AIM though. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Survey: Chat and IM
    ... >But don't think banning aim is easy as a firewall rule. ... >default port AIM uses, problem fixed right. ... >to search every port until it finds one it can>connect to aol servers ...
    (Security-Basics)
  • Re: REPOST of Re: [opensuse] OpenSuse 11
    ... inbuilt into Windows systems? ... | good router should have firewall software built in. ... before widnose has been started up, to keep your registry free from ... You can choose to grant only once, or remember decision, grant or denie. ...
    (SuSE)