The Active Network
ActiveWin Anonymous | Create a User | Reviews | News | Forums | Advertise | Career Portal | VBA in Excel | Users Online: 0  
 

Recommended Links:

Play your favourite online pokies and take what you win fast at the same day withdrawal online casinos in Australia.

Now, you can buy real Instagram followers.

AWBridal Highly Recommend Wedding & Bridesmaid Dress Online Store

light tower

buy arabic Twitter follower

buy spotify real followers

A great website to buy Facebook followers from is BRSM. They have a great track record!

the Binary Option Robot

Get Windows Tablet & Phones at DHgate.com

neowin.net

Amazon.com

  *  

Network Domain Name Issues?
Forum: Windows Server 2003
Read Only Forum
Back to Windows Server 2003
All Forums
  Displaying Posts 1 through 2 of 2
  This is an archived static copy of ActiveWin.com.
#1 By 84586 (209.180.120.98) at Wednesday, August 29, 2007 05:10:15 PM
First I am a novice when it comes it the "in's & out's" of Corporate Networking. So please bear with me. The issue is our IT guys have named the Internal Network Domain "mysite.com" Our website domain is also "mysite.com" As such we cannot access "mysite.com" from the Internet internally..."Page Cannot be Found" But we are able to access www.mysite.com I can access mysite.com from home outside our network I am the web admin and have requested that the internal network domain be changed due to seen and unforeseen issues this can cause. I'm not sure of any specific issues with this other than I've heard it should not be setup this way. For instance, I've published a simple web form on our website which is scripted to email information to an email address. When set up to email joe@mysite.com the email is not sent. There are no problems sending it to any other email address i.e. joe@mydomain.com It just will not work with any address @mysite.com We are using Exchange Server internally for all email and not the email server provided by the hosting service. [b]Am I correct in assuming that the Internal Network Domain Name should not be mysite.com OR the same as our website domain name.[/b] [b]If this is correct is there an IT Network Guru who can briefly list some of the known issues with this type of implementation? [/b] TIA, KingDesign If you need any more information I am more than willing to provide all I can to help resolve this issue or provide answers to IT and management as to why this needs to be changed.

#2 By 81519 (124.176.107.113) at Friday, September 07, 2007 10:23:57 PM
[QUOTE]Originally Posted by KingDesign: First I am a novice when it comes it the "in's & out's" of Corporate Networking. So please bear with me. The issue is our IT guys have named the Internal Network Domain "mysite.com" Our website domain is also "mysite.com" As such we cannot access "mysite.com" from the Internet internally..."Page Cannot be Found" But we are able to access www.mysite.com I can access mysite.com from home outside our network I am the web admin and have requested that the internal network domain be changed due to seen and unforeseen issues this can cause. I'm not sure of any specific issues with this other than I've heard it should not be setup this way. For instance, I've published a simple web form on our website which is scripted to email information to an email address. When set up to email joe@mysite.com the email is not sent. There are no problems sending it to any other email address i.e. joe@mydomain.com It just will not work with any address @mysite.com We are using Exchange Server internally for all email and not the email server provided by the hosting service. [b]Am I correct in assuming that the Internal Network Domain Name should not be mysite.com OR the same as our website domain name.[/b] [b]If this is correct is there an IT Network Guru who can briefly list some of the known issues with this type of implementation? [/b] TIA, KingDesign If you need any more information I am more than willing to provide all I can to help resolve this issue or provide answers to IT and management as to why this needs to be changed. [/QUOTE] yep u are right. Best practice is to have your internal DNS server with a different domain name. ---------------------------------------------- Forsaken



 

  *  
  *   *
 
replica watches