Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
pfSense Forum
pfSense English Support
»
Packages
»
AIM issue
Username:
Password:
1 Hour
1 Day
1 Week
1 Month
Forever
Home
Help
Search
Login
Register
Pages: [
1
]
Go Down
« previous
next »
Print
Author
Topic: AIM issue (Read 1140 times)
0 Members and 1 Guest are viewing this topic.
qnoturas
Newbie
Offline
Posts: 3
AIM issue
«
on:
April 15, 2008, 08:03:31 am »
Hello all,
I am having an issue with the using AIM 6 and IMSpector. By default, AIM6 uses port 443 to connect securely to the AOL servers. IMSpector will not log any messages using this port. I had then tried to switch the port setting to 5190 where IMSpector does log. However I am unable to connect using this port on any pc's on my network. I then tried my old firewall appliance and tried an offsite location and they both worked with the old 5190 port. I am thinking it is a configuration problem but this is a fresh install of pfSense with only imspector and squid installed. I had also tried to setup a rule on the LAN to explicitly allow 5190 but with no luck....
This is a standard installation of pfSense with 2 NICs one a D-link(WAN) and the other 3-com(LAN). My PC is a P3 500 with 640MB of PC-100 RAM.
The packages I have installed are: Squid and IMspector.
Help!!!!!!!
«
Last Edit: April 15, 2008, 08:18:32 am by qnoturas
»
Logged
hoba
Administrator
Hero Member
Offline
Posts: 5844
What was the problem to this solution again?
Re: AIM issue
«
Reply #1 on:
April 15, 2008, 08:27:07 am »
Are you runing squid in transparent mode?
Logged
qnoturas
Newbie
Offline
Posts: 3
Re: AIM issue
«
Reply #2 on:
April 15, 2008, 08:58:30 am »
I did have squid installed and running in transparent mode.
I have uninstalled squid and it is still an issue. I had installed squid in attempt to fix the issue because I had to use it with IP cop to get IMspector to work.
I now know that IMspector works without squid cause MSN still logs
Logged
qnoturas
Newbie
Offline
Posts: 3
Re: AIM issue
«
Reply #3 on:
April 16, 2008, 05:33:35 am »
*bump*
--Update--
I have reinstalled the pfSense and only added in IMspector. If I enable the protocol listener to everything minus ICQ/AIM, the AIM client will connect fine over 5190 however. If I enable the protocol listener, ICQ/AIM, I am unable to connect un til I disable the protocol. Is there a firewall rule I am missing? Please help.....
Logged
rsw686
Global Moderator
Sr. Member
Offline
Posts: 522
Re: AIM issue
«
Reply #4 on:
April 16, 2008, 09:56:05 pm »
AIM 6 uses a new version of the AIM/ICQ protocol which is not supported by IMSpector. Try an older version of AIM or ICQ and it should work fine.
Logged
Pages: [
1
]
Go Up
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
Administrative
-----------------------------
=> Forum rules
=> Messages from the pfSense Team
=> Feedback
-----------------------------
pfSense English Support
-----------------------------
=> Installation and Upgrades
=> General Questions
=> 2.1 Snapshot Feedback and Problems
=> Post a bounty
===> Completed Bounties
===> Expired/Withdrawn Bounties
=> Hardware
=> Firewalling
=> NAT
=> CARP/VIPs
=> Routing and Multi WAN
=> Traffic Shaping
=> DHCP and DNS
=> IPv6
=> IPsec
=> PPTP
=> PPPoE Server
=> Captive Portal
=> webGUI
=> Wireless
=> SNMP
=> Packages
=> Virtualization installations and techniques
=> OpenVPN
=> Gaming
-----------------------------
Development/Documentation
-----------------------------
=> Documentation
=> Development
-----------------------------
General Category
-----------------------------
=> General Discussion
-----------------------------
International Support
-----------------------------
=> Indonesian
=> Deutsch
=> Español
=> Français
=> Italiano
=> Russian
=> Nederlands
=> Norwegian
=> Portuguese
=> Polish
=> Romanian
=> Swedish
=> Turkish
-----------------------------
Retired
-----------------------------
=> 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
=> 1.2.1-RC Snapshot Feedback and Problems-RETIRED
=> 2.0-RC Snapshot Feedback and Problems - RETIRED
=> DNS Server testing area - RETIRED
Loading...