Re: companyweb from RWW
- From: Kline <Kline@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 30 Apr 2006 07:43:01 -0700
Thanks again. I tried
"telnet server.domain.com:444"
from the Internet and got the following:
"Could not open connection to the host, on port 23: connect failed."
I double checked the router/firewall and there is an entry
"HTTPS 192.168.1.107 * 444/444"
I believe this routes the public port 444 to the private port
192.168.1.107:444.
I dont' understand "port 23" in the error message.
--
Thanks,
KP
"Les Connor [SBS Community Member - SBS M" wrote:
So you need to port forward port 444 from your public IP address to your SBS.
IP address.
You need to run the CEICW and ensure the certificate is named
server.domain.com.
Then, from the internet - https://server.domain.com:444 has to hit
Companyweb. If it doesn't then port 444 is blocked. Either the port forward
isn't correct, or the ISP blocks it. telnet server.domain.com:444 from the
internet should tell the tale, it's open or it's not.
Publishing the default web site would result in http://server.domain.com
bringing it up from the outside, but that's not recommended. This site is
normally identified as 'Default' in IIS. Have you somehow modified it? If
you have port 80 open to the internet (not recommended) then
http://server.domain.com would hit this site without you altering anything.
Note that the URLs are different from within the lan, versus from the
internet. That's the way it should be. Don't try to access companyweb with
the same URL internally as you do externally.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Kline" <Kline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:27F1E419-D24E-4B2A-AB98-40B6001EFF8B@xxxxxxxxxxxxxxxx
I'm having a little bit of trouble with terminology here. "Internal
website"
means companyweb the way I'm using it. Let me review terminology.
->companyweb is reached by browsing to http://companyweb from a client PC
on
the LAN
->"Welcome to Windows" page (WTW) is reached by browsing to
http://server.domain.com from a client PC on the LAN
->The WTW default page has 4 links one of which points to the companyweb
with the URL http://companyweb.
->I have modified the WTW default page so that the link which points to
the
companyweb points to the URL https://server.domain.com:444. This is so
that
external users can reach the companyweb from the WTW page using this link.
I checked IIS and found the following websites on the SERVER:
Description, ID, State, Host Header Value, IP Address, Port, SSL Port,
Status
server.domain.com, 1, running, " ", *All Unassigned*, 80, 443, " "
MS SharePoint Admin, 2, running, " ", 192.168.1.107, 6358," "," "
SharePoint Central Admin, 3, running, " ", 192.168.1.107, 8081," "," "
companyweb, 4, running, companyweb, 192.168.1.107, 80, 444, " "
server.domain.com is my registered public domain name with static IP
address
provided by my ISP. I can successfully browse to the WTW web page from
the
Internet and from a client PC on the LAN. My problem is I can't reach the
internal companyweb using the URL https://server.domain.com:444.
--
Thanks,
KP
"Les Connor [SBS Community Member - SBS M" wrote:
I think you've made some mods somewhere? ... inline.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Kline" <Kline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C6BA1777-A527-4B5E-BABF-A9002B203853@xxxxxxxxxxxxxxxx
Thanks again, Les.
When I ping 'companyweb' from a client PC on the LAN I get
192.168.1.107
which is the IP address of the server.
This is the correct response.
When I browse to http://companyweb from a client PC on the LAN I get
the
internal website.
What is the 'internal website"? Is that something you added?, or do you
mean
Companyweb, or do you mean the Welcome to Windows (default internal
website?).
When I run the command "telnet SERVER 444" from a client PC on the LAN
I
get
a blinking cursor.
That's a correct response.
When I browse to http://server.domain.com from a client PC on the LAN I
get
the "Welcome to Windows Small Business Server 2003" webpage with four
links,
"My Company's Internal Web Site", "Network Configuration Wizard",
"Remote
Web
Workplace", "Information and Answers".
Is you internal domain name domain.com - is that the same as your public
domain? This site is the default web site. http://servername should bring
this up.
When I then click on the link "My Company's Internal Web Site" from a
client
PC on the LAN it tries to load "https://server.domain.com:444" but I
get a
page that says "The page cannot be displayed - The page you are looking
for
is currently unavailable..."
From the default web site, the url for My Company's Internal Web Site
(which
is companyweb) should just be http://companyweb. Have you modified this?
If you go into IIS and click on web sites - can you list what you see in
the
right pane? Name of site - host header values (if any) - and ports?
--
Thanks,
KP
"Les Connor [SBS Community Member - SBS M" wrote:
When on the lan, server.domain.com isn't going to work.
What do you get when you 'ping companyweb' from the server, or from a
workstation on the lan? - ip of SBS should be the result
What do you get when you run http://companyweb from the server, or
from a
workstation on the lan? - you should get companyweb site
What do you get when you telnet <servername> 444 from the server or a
workstation? - you should get a blinking cursor
If any of the above don't work, then there is a misconfiguration.
The above won't explain why external access doesn't work, but first
you
need
to know it works internally.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll
understand." - Confucius
"Kline" <Kline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CDBF7B9C-5AF6-488D-8C6C-F1B5F5B0E948@xxxxxxxxxxxxxxxx
The configuration is as follows:
-single nic on server
-router with firewall
-Broadband internet connection (2 way satellite, Direcway)
I tried this at the command line at a client PC:
telnet server.domain.com 444
and I got this:
Connecting to server.domain.com...Could not open connection to the
host,
on
port 444: Connect failed
I browsed to my router at 192.168.1.1 and checked the firewall to be
sure
it
is allowing connection to port 444 and the firewall rules table
included
the
following entry:
Allow HTTPS source:WAN,* destination:LAN, 192.168.1.107
protocol:
*,444
I did an "ipconfig /all" at the server and got the following:
C:\Documents and Settings\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . : klineproperties.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : klineproperties.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-13-72-0B-FF-45
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.107
Primary WINS Server . . . . . . . : 192.168.1.107
--
Thanks,
KP
"Les Connor [SBS Community Member - SBS M" wrote:
The web page link has nothing to do with it.
From the internet, https://fqdn:444 will go to companyweb providing
a)
port
444 is open (you can telnet fqdn 444 and see) and b) you elected to
make
the
site available in CEICW, and c) fqdn resolves to your public IP,
and
e)
you're correctly forwarded 444 from the public interface to your
SBS
external nic IP (if two NICS), or SBS nic (if one nic).
What's the network topology - number of nics, external device
(router,
firewall, broadband device - etc.). Perhaps an ipconfig/all run
from
the
server would be of use.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll
understand." - Confucius
"Kline" <Kline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8064D88A-D803-4049-90D8-173D30438A12@xxxxxxxxxxxxxxxx
Sorry, I have the "s" in the web page link. I just didn't have
it
in
the
forum message. Still doesn't work. Any other ideas? Perhaps a
corrupted
file somewhere?
--
Thanks,
KP
"Les Connor [SBS Community Member - SBS M" wrote:
https://server.domain.com:444 might work - notice the "s" after
http.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me
and
I'll
understand." - Confucius
- Follow-Ups:
- Re: companyweb from RWW
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: companyweb from RWW
- References:
- Re: companyweb from RWW
- From: Kline
- Re: companyweb from RWW
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: companyweb from RWW
- Prev by Date: Re: Message to Frank McCallister
- Next by Date: Re: LDAP on SBS2003
- Previous by thread: Re: companyweb from RWW
- Next by thread: Re: companyweb from RWW
- Index(es):
Relevant Pages
|
|