Solved

remote.mydomain.com sub domain issues

Posted on 2013-07-01
5
262 Views
Last Modified: 2013-07-03
Hi all,

Quick question, if I  ping <servername> from inside the network I get

192.168.0.3 (which is correct).

If I ping remote.<ourdomain>.com from inside the network for some reason i get 192.168.0.2?

However is I access https://remote.<ourdomain>.com/remote from outside the network it load just fine?

TOp and bottom is when I am inside the network for some reason it is associating remote. with .0.2 instead os .0.3 what coudl be causing this redirection?
0
Comment
Question by:flynny
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 

Author Comment

by:flynny
ID: 39290345
oh an dby the way just to add I have checked the hosts file but this has nothing referencing it.
0
 
LVL 81

Accepted Solution

by:
David Johnson, CD, MVP earned 500 total points
ID: 39290772
check your dns records.

nslookup remote.domain.com should resolve to 192.168.0.3

There are ways within iis i.e. 301 redirect  to have remote.domain.com point to 192.168.0.2 and the webserver on 192.168.0.2 redirect all requests to 192.168.0.3
0
 

Author Comment

by:flynny
ID: 39296368
@ve3ofa

if i nslookup form RDP on the server it is resolving to 192.168.0.2 rather than .0.3

where do i check to change this in IIS please?
0
 

Author Comment

by:flynny
ID: 39296378
Hi i have managed to resolve it with you help.

There was a forward lookup zone redirecting to .0.2.

I have ammended this to be .0.3
0
 

Author Closing Comment

by:flynny
ID: 39296379
many thanks for the prompt response.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A lot of problems and solutions are available on the net for the error message "Source server does not meet minimum requirements for migration" while performing a migration from Small Business Server 2003 to SBS 2008. This error pops up just before …
Because virtualization becomes more and more common, and, with Microsoft Hyper-V included in Windows Server at no additional costs, and, most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 201…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question