how to configure the outlook express on proxy client machine


Recommended Posts

Hi All,

total 4 machine one of the AnalogX proxy server machine (win_2k3) [this is not Exchange server]

and 3 machine AnalogX proxy Client -- All site's working properly on client machine

i access the POP3 account over the internet

e.g one is my account = user1@kss.com

this account i configure on proxy server machine

POP3= mail.kss.com

SMTP= mail.kss.com

working fine

but saveral configuration on my client machine not working properly

my server machine ip address in 10.xx.xx.xx range

plz help me

You have more problems with this proxy than anyone I've ever heard of or personally met.

Include what you are getting for error messages on the client so we know what's actually happening. What does the log on the server say (AnalogX keeps a log file if it's enabled) and do you have the POP3 option enabled?

  Ghost96 said:
You have more problems with this proxy than anyone I've ever heard of or personally met.

Include what you are getting for error messages on the client so we know what's actually happening. What does the log on the server say (AnalogX keeps a log file if it's enabled) and do you have the POP3 option enabled?

See the Image

When i configure user1@kss.com on proxy server machine (on outlook) then i got the access send and receive mail over the internet

but when i try to configure saveral setting on client machine (outlook)

conneting pop3 mail server failed

post-248694-1206622926_thumb.jpg

post-248694-1206623687.jpg

Your screenshots don't help; answer my questions

Once again:

What does the log file on the server say that is running AnalogX?

Is the POP3 option enabled in the software itself?

I'm not interested in your client settings - what I am asking for is on the AnalogX app itself.

What does the log file on the server say that is running AnalogX?

Is the POP3 option enabled in the software itself?

On my Analog x proxy server site all port like POP,SMTP.HTTP,NNTP,FTP,SOCKS are enbled

and also configured Email Alias's

Email ID= user1@kss.com

POP= mail.kss.com

SMTP= mail.kss.com

post-248694-1206682630.jpg

You see where it say Logging is Enabled?

Post the log file after you try to connect to the POP3 server so we can see what the log file says is happening during that operation. The log files exists in the same folder that you installed the application.

/sigh

I don't want that client error. I want the posting of the log file that exists in the same folder that you installed AnalogX's Proxy software in. That's where the log file resides for the proxy. That's what I care about.

Let me even be more specific. Post "proxy.log" from wherever you actually installed that software to. If you want to email it to me, PM me and I'll give you my address. You don't have to post the whole thing. I just want the part captured that shows where you are having the problems here.

Is your proxy icon green or red?

Edited by Ghost96
  • 5 months later...

Hi,

I have a broadband connection in 1 system and 3 clinets connected through lan.

I have download the analogx proxy software so that i can have internet acess in all the machines in the network. With the help of readme file i have configured the internet explorer and been able to browse net in all the machine.

But i am unbale to send/receive email even after configuring the email alias and mircosoft outlook in my client machine as per the readme file.

Following is my configuration in Analog proxy and outlook in client machine:-

Analog Proxy-

1)All services are On

2)proxy binded

2)Email Configuration

name@dataone.in

wmma.dataone.in

wmra.dataone.in

2)Mricosoft Outlook 2003-Client Machine

1)Email address- name@dataone.in

2)User Name name@dataone.in

Password- xxxxxxx

3) Incoming Server Ip add 192.168.0.112

Out going server IP add 192.168.0.112

Follwing erroe Message shown while sending mail:

our message did not reach some or all of the intended recipients.

Subject: Test Mail

Sent: 14-Sep-2008 10:57 AM

The following recipient(s) could not be reached:

'name@eth.net' on 14-Sep-2008 10:57 AM

550 5.7.1 Relaying not allowed: name@eth.net

Following is the proxy log file-

09/14/2008 10:30:38.640: Proxy Server (v4.14 - Release) Starting with Services (0xFFFFFFFF)

09/14/2008 10:30:39.328: FTP listen started (21)

09/14/2008 10:30:39.640: NNTP listen started (119)

09/14/2008 10:30:40.078: SMTP listen started (25)

09/14/2008 10:30:40.343: POP3 listen started (110)

09/14/2008 10:30:40.593: HTTP listen started (6588)

09/14/2008 10:30:40.859: SOCKS listen started (1080)

09/14/2008 10:30:51.609: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:30:53.781: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:03.203: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:04.484: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:04.687: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:05.343: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:06.343: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:06.734: 18043028 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:07.125: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:07.218: 18064396 - HTTP Closing socket (3)

09/14/2008 10:31:07.343: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:07.375: 4094388 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:10.640: 4079828 - HTTP Closing socket (4)

09/14/2008 10:31:10.812: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:11.484: 18064396 - HTTP Closing socket (4)

09/14/2008 10:31:12.328: 4079828 - HTTP Closing socket (3)

09/14/2008 10:31:20.265: 18043028 - HTTP Closing socket (2)

09/14/2008 10:31:32.640: 4094388 - HTTP Closing socket (1)

09/14/2008 10:31:32.703: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:34.484: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:34.687: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:34.718: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:35.109: 18064396 - HTTP Closing socket (2)

09/14/2008 10:31:38.859: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:38.921: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:41.296: 4079828 - HTTP Closing socket (1)

09/14/2008 10:31:41.812: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:31:44.453: 4079828 - HTTP Closing socket (1)

09/14/2008 10:33:54.484: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:33:54.640: 4079828 - HTTP Closing socket (1)

09/14/2008 10:33:59.812: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:34:02.078: 4079828 - HTTP Closing socket (1)

09/14/2008 10:34:10.078: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:34:13.796: 4079828 - HTTP Closing socket (1)

09/14/2008 10:34:17.437: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:34:22.062: 4079828 - HTTP Closing socket (1)

09/14/2008 10:35:35.125: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:35:40.890: 4079828 - HTTP Closing socket (1)

09/14/2008 10:35:48.671: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:35:51.375: 4079828 - HTTP Closing socket (1)

09/14/2008 10:35:51.859: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:35:56.375: 4079828 - HTTP Closing socket (1)

09/14/2008 10:36:22.937: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:24.343: 4079828 - HTTP Closing socket (1)

09/14/2008 10:36:29.312: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:32.125: 4079828 - HTTP Closing socket (1)

09/14/2008 10:36:45.015: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:45.343: 4079828 - HTTP Closing socket (1)

09/14/2008 10:36:47.640: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:48.093: 4079828 - HTTP Closing socket (1)

09/14/2008 10:36:54.937: 4079828 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:57.750: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:36:58.031: 18064396 - HTTP Closing socket (2)

09/14/2008 10:36:59.859: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:37:01.750: 18022524 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:37:03.328: 18022524 - HTTP Closing socket (3)

09/14/2008 10:38:00.140: 18064396 - HTTP Closing socket (2)

09/14/2008 10:38:02.015: 4079828 - HTTP Closing socket (1)

09/14/2008 10:38:50.937: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:38:51.062: 18064396 - HTTP Closing socket (1)

09/14/2008 10:56:31.296: 18064396 - SMTP Client connection accepted from 192.168.0.111

09/14/2008 10:56:31.343: 18064396 - SMTP Unknown command 'EHLO Gladerma'

09/14/2008 10:56:31.734: 18064396 - SMTP Connection between local and remote established 'wmra.dataone.in:25'

09/14/2008 10:56:32.671: 18064396 - SMTP Remote closed connection [read]

09/14/2008 10:56:32.671: 18064396 - SMTP Closing socket (1)

09/14/2008 10:56:32.703: 4094140 - POP3 Client connection accepted from 192.168.0.111

09/14/2008 10:56:32.859: 4094140 - POP3 Connection between local and remote established 'wmma.dataone.in:110'

09/14/2008 10:56:47.281: 4094140 - POP3 Local closed connection [read]

09/14/2008 10:56:47.281: 4094140 - POP3 Closing socket (1)

09/14/2008 10:56:55.796: 4094140 - SMTP Client connection accepted from 192.168.0.111

09/14/2008 10:56:55.796: 4094140 - SMTP Unknown command 'EHLO Gladerma'

09/14/2008 10:56:55.796: 4094140 - SMTP Connection between local and remote established 'wmra.dataone.in:25'

09/14/2008 10:56:59.125: 4094140 - SMTP Local closed connection [read]

09/14/2008 10:56:59.125: 4094140 - SMTP Closing socket (1)

09/14/2008 10:58:07.968: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 10:58:13.656: 18022524 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:02:58.062: 18022524 - HTTP Closing socket (2)

09/14/2008 11:03:03.062: 18064396 - HTTP Closing socket (1)

09/14/2008 11:06:45.765: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:46.625: 18022524 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:47.281: 18064396 - HTTP Closing socket (2)

09/14/2008 11:06:47.484: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:48.468: 18022524 - HTTP Closing socket (2)

09/14/2008 11:06:48.734: 18022524 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:53.937: 18023932 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:54.375: 18023932 - HTTP Closing socket (3)

09/14/2008 11:06:54.718: 18023932 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:55.125: 18064396 - HTTP Closing socket (3)

09/14/2008 11:06:55.187: 18064396 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:55.609: 18025932 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:55.671: 18026268 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:56.125: 18025932 - HTTP Closing socket (5)

09/14/2008 11:06:56.250: 18026268 - HTTP Closing socket (4)

09/14/2008 11:06:57.125: 4097580 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:57.484: 18025932 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:57.890: 18025932 - HTTP Closing socket (5)

09/14/2008 11:06:57.890: 4097580 - HTTP Closing socket (4)

09/14/2008 11:06:57.906: 18023932 - HTTP Closing socket (3)

09/14/2008 11:06:58.125: 18064396 - HTTP Closing socket (2)

09/14/2008 11:06:58.328: 4097580 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.343: 18025932 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.343: 4097972 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.359: 4093868 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.703: 4097580 - HTTP Closing socket (5)

09/14/2008 11:06:58.703: 4097972 - HTTP Closing socket (4)

09/14/2008 11:06:58.718: 4093868 - HTTP Closing socket (3)

09/14/2008 11:06:58.734: 4097972 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.750: 4097580 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:06:58.859: 18025932 - HTTP Closing socket (4)

09/14/2008 11:06:59.109: 4097972 - HTTP Closing socket (3)

09/14/2008 11:06:59.109: 4097580 - HTTP Closing socket (2)

09/14/2008 11:06:59.546: 4097972 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:07:03.125: 4097972 - HTTP Closing socket (2)

09/14/2008 11:07:04.375: 4097972 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:07:34.734: 4097972 - HTTP Closing socket (2)

09/14/2008 11:07:37.687: 4097972 - HTTP Client connection accepted from 192.168.0.111

09/14/2008 11:07:38.531: 4097972 - HTTP Closing socket (2)

I will be very greatful if u can guide me or help in resoving the above problem.

Will be egarly waiting for response and this is the first time i have tried something in this field as i have every limited in this field

Thanks a lot

  • 3 weeks later...

Hi,

Forget the Analog X Porxy Software, this software are better when you only access the web (http) but not good for accessing mail (POP/IMAP)

You configure the VPN setting on your currently proxy server using RRAS

An provide ip address of RRAS server to client default gateway

remove proxy setting on client machine which u configured

only select " detect proxy setting automatically.

Now Enjoy mail access

Goood Luck.....

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The so called tri-fold phone is not a phone just like today's so called smartphones are not phones. They are computing camera devices with the ability to make and receive phone calls. For many the phone app is among the least used apps on these so called smartphones.
    • Backpack Hero and Figment are free to claim on the Epic Games Store by Pulasthi Ariyasinghe The Epic Games Store has just refreshed its weekly giveaways promotion, and there are two games up for grabs this time. Replacing the Sable freebie from last week, Backpack Hero and Figment have now landed for all PC gamers to claim. As always, you have seven days to add the latest indie game permanently to your Epic Games Store library. From the double giveaway, Backpack Hero comes in from indie developer Jaspel, offering a unique inventory management roguelike experience. Aside from collecting items to maximize the potential of a run, like with other roguelikes, here, your placement of the item in the backpack also matters. Each run offers randomly generated dungeons, enemies, and loot to grab. Next, Figment lands from Bedtime Digital Games. This isometric perspective action adventure game takes place in a surreal landscape with hand-drawn artwork, and everything is taking place inside a mind. You take the role of Dusty, the former voice of courage in the mind. The musical adventure involves trying to return Dusty to his old self while also helping the mind beat back its nightmares and restoring its original purpose. The Figment and Backpack Hero giveaways on the Epic Games Store are now active, and they will last until July 10. When not on sale, both games come in at $19.99 to purchase, but PC gamers can add the duo to their library for no cost during the seven-day timeframe. When the giveaways refresh next week, Epic Games plans on giving away two more games: the next musical adventure, Figment 2: Creed Valley, as well as the classic arcade-inspired shoot’em up Sky Racket.
    • Isn’t your Google Wallet full of your personal information tied to your identity?
  • Recent Achievements

    • Week One Done
      Devesh Beri earned a badge
      Week One Done
    • Week One Done
      956400 earned a badge
      Week One Done
    • First Post
      loose_observer earned a badge
      First Post
    • Week One Done
      BeeJay_Balu earned a badge
      Week One Done
    • Week One Done
      filminutz earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      451
    2. 2
      ATLien_0
      158
    3. 3
      +FloatingFatMan
      153
    4. 4
      Nick H.
      65
    5. 5
      +thexfile
      62
  • Tell a friend

    Love Neowin? Tell a friend!