Re: Newbie DNS resolution question

Bruce D <BruceD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Ok, Kevin, I obviously omitted a few details: First, the company
> _does_ own companyname.com, and remote.companyname.com is currently
> up and running from the Internet. Their DNS is hosted by a
> third-party web hosting company, who has the remote.companyname.com
> properly resolving from outside the firewall.
>
> The question is, exactly how do I get remote.companyname.com to
> resolve to 192.168.x.y on the internal DNS?

I assume you have a router?
In your router, forward incoming requests on port 80 TCP 443 TCP for SSL, to
the IP of the web server. This is labeled differently depending on the
router manufacturer.

Remote desktop uses 3389 TCP, so if you have one IP and multiple remote
desktops, you'll need to modify the remote desktop on each PC to listen on a
different port, because 3389 will go to one computer only, for additional
computers you may want to use 3390, 3391, etc. then forward that particular
port to the proper workstation.
However, if you set up a VPN server, you need only 1723 TCP forwarded to the
VPN server then user access their machines by entering the actual internal
IP of their workstations only in the RDP client. Without a VPN they need to
enter the public IP with the port that goes to their workstation, e.g.
80.81.81.81:3390 and so on into the client..


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.

Relevant Pages

  • Re: uucp via tcp through firewall fails
    ... >and now uucp via tcp fails. ... >UNIX system. ... as bad as having it directly exposed to the internet. ... recall that I had to enable ident and open a port for it 113/TCP. ...
    (comp.unix.sco.misc)
  • RE: [Error number: 0x80072EFD] auto update wont work
    ... In Internet Access Control go onto Microsoft Generic Host Process for Win32 ... remote http ... remote https (port 443) ... NB re TCP and UDP - some sites say you only need TCP but I found you need ...
    (microsoft.public.windowsupdate)
  • RE: Windows XP open port 389
    ... Internet Connection Sharing in WIN XP should use NAT (Network Address ... Windows XP open port 389 ... I believe the Internet Locator Service cannot be installed on Windows ... 389 Internet Locator Service TCP ...
    (Focus-Microsoft)
  • Re: honeypot
    ... That allows me to see new malware port hunting. ... 66.120.0.0-66.127.255.255 # SBC Internet Services SBCIS-SIS80 ... 66.144.0.0-66.145.255.255 # State of Ohio Network Columbus OH ...
    (comp.security.misc)
  • RE: firewall
    ... You need to do a lot of reading about ipfw ... IPFW is the only firewall available to FBSD, ... rules do not function correctly on a DSL or cable internet ... @320 pass in quick on rl0 proto tcp from 63.70.155.0/24 to any port ...
    (freebsd-questions)