cannot access our website from outside the lan

[mucous]

Hi,

We just migrated to Win2k servers and workstations. Our office website is hosted outside the office lan on the Internet and we are not able toreach it. The new network was rolled out about two weeks ago and we had no problems accessing our hosted site from the lan.
At some point, we are planning to bring the site inhouse, so during the rollout, we decided to give our server the same domain name as the website, then made an entry in DNS to identify our outside website for the time being. This appeared to have worked for a while, but all of a sudden, now it won't pull up when trying to get to the site. We're also having trouble getting to outside webmail enabled sites that our users have for personal email.
The initial setup was done by a consultant who is now gone.
I'm afraid I'm not terribly knowledgable in this area and could use some help. The consultant has done some looking around too, but is also stumped on this. We are running a sonicwall pro firewall also and he says everything looks correct to him.

I'd sure appreciate any suggestions as to where to look to resolve this dilemma. My office is beginning to get a wee bit perturbed about this!

 

[mucous]

Woops! I meant we can't access our website from WITHIN our lan. Sorry

 

[mucous]

Ok


The problem was with our Internet Service Provider. All is well...

 

[gilvie]

Hi Mviker,

I am sort of having the same problem, but I want to access my website ( From inside ) as if I were on the outside.
sound confusing?
As if I was my client trying to get.
I know I could probably have a dial up connection to test internally, but is there a website where you could go and ping your IP as if you were outside?

 

[nhat]

hi there
it is probaby you are install AD use the zone same as your interent domain name. like if you have company.com as your public website and when you install Active directory you also use company.com as your AD dns name. you will see that problem. if you change to use something like company.local or else. it will solve problem

 

[wbg34]

Gilvie,
If you are using the same domain name for your internal domain and web domain like nhat described you will have that problem. The simplest way to fix this is to add a new host in your forward lookup zone named

http://www with

your server's internal ip for its address.