Accessing Sites Internally vs. Externally

[John A. Janes]

Here's an odd one, I'm currently developing a site for internal usage, to get
around their public website, I set the internal server to port 8080 (I
publish my .net from my office externally). There is no problem at all
accessing the site externally, but it is almost impossible to access
internally. I checked to make sure I have no references in the site to the
external publishing address. This may be a very simple problem, but one I
have yet to find an answer to. Thanks in advance!
--
John A. Janes
john<removeme><shift-2>naisnet<dot>com

[Patrice]

And the error you see is ? What do you mean by "almost impossible" ? Does it
have the expected IP address ?

You could try also an IIS group. Looks more like a site or network
configuration problem.

Patrice

--

"John A. Janes" <Jo********@discussions.microsoft.com> a écrit dans le
message de news:AD**********************************@microsof t.com...

Here's an odd one, I'm currently developing a site for internal usage, to get around their public website, I set the internal server to port 8080 (I
publish my .net from my office externally). There is no problem at all
accessing the site externally, but it is almost impossible to access
internally. I checked to make sure I have no references in the site to the external publishing address. This may be a very simple problem, but one I
have yet to find an answer to. Thanks in advance!
--
John A. Janes
john<removeme><shift-2>naisnet<dot>com

[John A. Janes]

"Almost Impossible" = any page where I have a decent amount of .net code
takes up to 10 minutes to load, if at all (It loads about 15% of the time).
Pages not containing .net code load without error, and pages accessed
externally load without error.

I've checked all of the network settings, accessed it internally via 1)
Netbios Machine Name; 2) Raw IP Address and 3) the External name with the
same results.
"Patrice" wrote:

And the error you see is ? What do you mean by "almost impossible" ? Does it
have the expected IP address ?

You could try also an IIS group. Looks more like a site or network
configuration problem.

Patrice

--

"John A. Janes" <Jo********@discussions.microsoft.com> a écrit dans le
message de news:AD**********************************@microsof t.com...

Here's an odd one, I'm currently developing a site for internal usage, to

get

around their public website, I set the internal server to port 8080 (I
publish my .net from my office externally). There is no problem at all
accessing the site externally, but it is almost impossible to access
internally. I checked to make sure I have no references in the site to

the

external publishing address. This may be a very simple problem, but one I
have yet to find an answer to. Thanks in advance!
--
John A. Janes
john<removeme><shift-2>naisnet<dot>com