Re: WSS v.3 BETA 2 - FQDN REQUIRED for external access?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

ok, you've got me confused on some of the details here.

Under "Add Incoming URL's" there is just one space for "New default zone URL
protocol, host and port."

I see no settings under "Add Incoming URL's" for extranet zone or outgoing
URL.

Sorry to keep hounding you on this and the details but this is the first
time I've EVER used SharePoint in any form.



"Todd Klindt" wrote:

Jess,
Good catch, I screwed the first post up. You need to create a new Incoming
URL. At least that's what I had to do when I wanted mine to work
externally. Create it for the Extranet zone and set a corresponding
Outgoing URL. WSS has some really neat things you can do with Zones and
stuff that I haven't gotten up to speed on yet. I think the Incoming URL
will get you closer to getting your stuff working.

tk
"Jess" <Jess@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A11B34C3-FD40-4761-AC91-E8C931A6A8F7@xxxxxxxxxxxxxxxx
Now I can get to it, Todd. I'm pretty sure I tried that from your previous
reply on my post on Page 6. Your showing the main Alternate Access Mapping
page and to use the "Create External URL Mapping" button by what you have
circled.

On the actual "Create External URL Mapping" page does it matter what I put
for "Resource Name"? Does it need to be the server name or internal IP or
can
it be whatever I want? I.e. SharePoint Test?

For "New default zone URL protocol, host and port" do I put the external
IP
address? I.e. http://123.456.789.123?



"Todd Klindt" wrote:

Read this and see if it helps,
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=18. I know it's
necessary for FQDNs, but you might need it for straight IPs too.

tk
"Jess" <Jess@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F4418D8-A03D-4275-A13D-8DBE89362C46@xxxxxxxxxxxxxxxx
Question was not will FQDN work -- sure it'll work, if I have one --
but
can
WSS be accessed externally using it's IP address (the external address
in
the
firewall which NATs to it's internal address that is in DNS with it's
//servername) and NOT a FQDN?

I installed this server over a week ago and still cannot access it from
the
outside and I'm wondering if it's because we don't have a FQDN for it
and
are
using an IP. I could just be going in circles trying to access it and
never
will be able to using the IP.

"Bob Fox" wrote:

The DNS wont help you because its an Internal DNS and the outside has
no
idea what this is. What is your NAT address ? You can problably
access
it
that way until you get an external DNS registered but as you say its
only
a
test sight so spending the money may not be worth it.

So for a quick answer the FQDN wont work because there are no external
DNS
servers that are aware of this domain or system. Hope this helps


--
Bob Fox
Web Site http://bobfox.net
Blog Site http://sharepointblogs.com/bobfox

"Jess" <Jess@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E74F4918-CA87-4F12-A8C4-7CFEA3840A9F@xxxxxxxxxxxxxxxx
Trying to access a test server we set up to try out WSS v.3 BETA 2
from
externally. We havn't registered a name for the server since it's a
test.
So
we're just using an IP address from our block of IP's to get to it
externally. Is this possible or does it HAVE to have a
name.domain.com
to
access it externally?

I entered the server name and IP in Server 2003 DNS record. I mapped
the
external address to the internal address via NAT in the hardware
firewall.

When I type in the IP address externally and hit go I'm presented
with
the
login window and it shows up in the firewall log as an "allow", I
enter
in
the domain\username and password and the login window goes away and
I
get
"This page cannot be displayed" in IE7. Another look at the firewall
log
shows nothing, no allows or denies or any traffic for the server/IP.
Just
the
one entry from the login window. Also I'm only getting the login
window
once
so I'm thinking it's accepting the credentials as I've tried using
the
wrong
credentials and I get 3 tries. Whereas with the correct credentials
I'm
getting one try before getting "page cannot be displayed".

So is it possible to access the SharePoint Services server
externally
using
an IP address and not a FQDN?










.

Relevant Pages

  • Re: Cross Post from ActiveSync Newsgroup - Problem Resolving Internal and FQDN Addresses when Us
    ... create a DNS zone on SBS for mail.thread.com, do not create a zone for ... parent' entry pointing to the internal IP of the server. ... with a Windows Mobile device in our SBS 2003 network. ... configuration to reference the FQDN? ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS v.3 BETA 2 - FQDN REQUIRED for external access?
    ... Under "Add Incoming URL's" there is just one space for "New default zone ... Does it need to be the server name or internal IP ... //servername) and NOT a FQDN? ... login window and it shows up in the firewall log as an "allow", ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Getting prompted on IIS web
    ... Add the FQDN to the intranet or trusted zone and the problem ought to go ... > We have run a .NET app on a test and prod server for months. ... > Authentication method has not changed, only the URL now uses the entire> domain name. ...
    (microsoft.public.inetserver.iis.security)
  • Re: 2k3 server DNS - _msdcs grayed out and not creating all necessary folders
    ... I just demoted the DC and checked the name of the server. ... I went in and set up a new Zone and i'm getting the same as before. ... one with the FQDN of the server and one just as server.. ... I'm getting the error in the DNS log stating that the DNS ...
    (microsoft.public.windows.server.dns)
  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)