[alexmadalo]

Is there a way in windows in which traffic with specified IP address and port number can be redirected from one computer to another on a Local Area Network?

[chuckhole]

You can port filter within the TCP/IP properties. Redirecting the traffic is a different animal. What type of traffic are you talking about?

Note: Generally, this type of practice is a form of hijacking and depending on the use and intent, you may have a legal issue to contend with.

[alexmadalo]

You can port filter within the TCP/IP properties. Redirecting the traffic is a different animal. What type of traffic are you talking about?

Note: Generally, this type of practice is a form of hijacking and depending on the use and intent, you may have a legal issue to contend with.

I must begin by stressing the point that the redirection of traffic I am trying to achieve has no malicious intent at all. It's for the benefit of all those on our LAN.

What I really wanted to redirect is incoming email so that it goes to the correct machine where we are running our email server. This server is supposed to get incoming mail on port 110 thus using POP3.

Thanks.

[chuckhole]

This is why I was asking what type of traffic. This is a common practice. What type of mail server do you use?

For example, MS Exchange uses an SMTP email connector that is configured to use a local upstream SMTP server or a "Smart Host". A Smart Host is something like your ISP in which it is capable of the "store and forward" of your email and requires a logon. The credentials would be embedded within your SMTP connector. The host ISP would receive all email destined for your domain an forward it on to your server. Your email server will have all of the mailboxes configured for your domain and will handle the internal mail delivery.

We use MS Exchange and an externally published SMTP server (MX and A records for domain and host name). It is configured to receive Port 25 traffic only from our ISP's mail servers and will not allow Open Relay (spammers). As far as sending email, the same server acts as a DNS caching server and Internet Proxy Server. The DNS caching server forwards all non-internal requests to the ISP's DNS server for name resolution. This includes resolving the domain name and MX records for the emails being sent out to the Internet for delivery.

Note that I have not mentioned a POP server? This is assuming that you are hosting your own email server. If you are not hosting your own email server (MAPI) then you will have to configure your email clients to connect directly to the remote ISP's POP and SMTP server.

[alexmadalo]

This is why I was asking what type of traffic. This is a common practice. What type of mail server do you use?

For example, MS Exchange uses an SMTP email connector that is configured to use a local upstream SMTP server or a "Smart Host". A Smart Host is something like your ISP in which it is capable of the "store and forward" of your email and requires a logon. The credentials would be embedded within your SMTP connector. The host ISP would receive all email destined for your domain an forward it on to your server. Your email server will have all of the mailboxes configured for your domain and will handle the internal mail delivery.

We use MS Exchange and an externally published SMTP server (MX and A records for domain and host name). It is configured to receive Port 25 traffic only from our ISP's mail servers and will not allow Open Relay (spammers). As far as sending email, the same server acts as a DNS caching server and Internet Proxy Server. The DNS caching server forwards all non-internal requests to the ISP's DNS server for name resolution. This includes resolving the domain name and MX records for the emails being sent out to the Internet for delivery.

Note that I have not mentioned a POP server? This is assuming that you are hosting your own email server. If you are not hosting your own email server (MAPI) then you will have to configure your email clients to connect directly to the remote ISP's POP and SMTP server.

The type of mail server we are using is VPOP3.

[chuckhole]

POP is a "store and forward" type of server. They typically do not retain the emails in a centralized storage but instead, forward the email when the client asks for it.

You can still host your own SMTP server. You can use Windows IIS with SMTP services if you like. It needs a connection to your ISP and your ISP will need to add a few DNS records for your SMTP server.

MX = Mail Exchanger for the host name
A = host name for the IP address
PTR = reverse address lookup for the host name