Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 398
  • Last Modified:

Firewall or Router problem

This is a strange question so I am not sure how to word it but I will try.

We have a small Network with 2 servers, one Terminal Server and an Exchange 2010 Server.
We have just had a new SQL application installed by a company.
All seems ok but now they want to be able to Telnet our Terminal Server which is where they installed there program using 2 different ports, 444 and 50495. I have set them up using Port Forwarding on the Router which is fine, but now they also want to Telnet this Server/ Application internally as well which is fine except they now want to Telnet this Server/app internally using the external/wan IP.

Im confused, my question is how do I setup the router to Telnet an Internal Server using an External IP Address. He mentions ISA Server, but I dont have an ISA Server.

Any help would be appreciated.
0
NWCCSteve
Asked:
NWCCSteve
1 Solution
 
bbaoIT ConsultantCommented:
what's the model of that router?
0
 
systanCommented:
hi,
Use a switch for the main network producer.

public ip: sample: 12.12.12.1 (wan)
from switch to your router (wan is connected to the switch,  lan is connected to terminal server/OR any server)

public ip: sample: 12.12.12.2
from switch to your server/app (of which this will have a new public ip address, not connected from the router)

So, they want the other server to be standalone as have the public ip address, so they can access it smoothly without problem.

Just got back in EE
Good Luck
0
 
Fred MarshallPrincipalCommented:
I may not understand.  It seems that opening a port for SSH would be the thing.  

I would not open my network to telnet in favor of SSH.

You might read this about it:
http://www.dd-wrt.com/wiki/index.php/SSH
0
 
BAYCCSCommented:
I am not sure of what kind of equipment you are running but in most cases you will not be able to use an external IP internally on your network because of this simple reason. When a workstation sends a request to an external IP the request passes out your router via the outside interface and then would have to come back in that same interface which the router will not allow to happen. Basically you can't go out and back in the same interface.

You would need to setup a domain name for the external IP address and use some form of split dns or dns doctoring that would translate the outside IP to the internal IP automatically.
0
 
NWCCSteveAuthor Commented:
Thanks Systan
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now