Re: Setting up Remote Web work place to acess from Internet
- From: "Costas" <cpstechgroup@xxxxxxxxx>
- Date: Fri, 22 Jun 2007 07:42:50 -0400
Goto dyndns.com and create a free account to setup a DNS record for dynamic IP addresses. Read the instructions and download the client software you'll find there and install it on your server. That software will be polling the IP address of the server and update the DNS entry automatically. You won't have to do anything else.
You might want to also check your router, because some routers do the same thing I described above for you (work with dyndns.com and update a dynamic IP address).
Costas
"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E647171B-5526-485B-BD8F-F8284A56F1BA@xxxxxxxxxxxxxxxx
I used whatismyip.com and found what my IP is . However when i Power off and
power on my Broadband modem the IP changes . and yes as you mentioned
192.168.1.1 is assigned by my dsl modem router.
So like you mentioned if i have to reach it from the internet via
https://yourpublicIP/remote. Do i need to know find my ip alwaysbefore using
the remote web , and also will creating a MX record help as my dynamic IP
keeps on changing . We always poweron the modem in the morning and power it
off in the evening
Any Tips on how to resolve this
Thanks
"Henry Craven {SBS-MVP}" wrote:
So let's get some of this terminology sorted out so we're all speaking the
same Technical Language and cut down on misunderstandings...
1st let's say you have 2 NICs ( Network Interface Cards )
These can be connected to Local Area Networks, Wide Area Neworks or the
Internet.
LAN's are Local Area Networks ( you have 2 of them too One "Inside" your
Domain that the Workstations are connected to ( 192.168.0.x subnet ) and one
"External"/ Internet Facing (192.168.1.x subnet) These are Local Area
Networks because 192.168.x.x is not internet routable.
Next, your 192.168.1.1 would not be asssigned by the ISP's DHCP but by your
DSL Modem/Router
Your ISP would assign you either a static or dynamic IP that you can
determine by examining the DSL Modem/Router or by going to whatismyip.com -
this is your Public / Internet interface.
Now, RWW has nothing to do with your Website. As in your case it is hosted
at GoDaddy and would be reached via an IP address that has nothing to do
with the Public IP of the SBServer so therefore you do not reach it via
Https://www.yourwebsite/remote .
You would reach it from the internet via https://yourpublicIP/remote.
OR
For a more friendly and rmemberable address you wouuld use your MX record
( assuming you have set one up so that you can receive email directly to
your exchange server )
This would look something like https://mail.yourpublicdomain/remote
( mail.yourpublicdomain needs to resolve to your publicIP Address )
You should also have created a Self Signed Certificate in that name when you
ran the CEICWizard.
------
Your MX records currently point to :
0 smtp.secureserver.net. [TTL=3600] IP=64.202.166.12 [CNAME] [US]
10 mailstore1.secureserver.net. [TTL=3600] IP=64.202.166.11
and your website is at 64.202.189.116
there are issues with that:
your MX records points to a CNAME. CNAMEs are prohibited in MX records,
according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3.
The problem MX record(s) are:
smtp.secureserver.net.->smtp.where.secureserver.net.->64.202.166.12
One or more of your mailservers is claiming to be a host other than what it
really is (the SMTP greeting should be a 3-digit code, followed by a space
or a dash, then the host name). If your mailserver sends out E-mail using
this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam
software. This is also a technical violation of RFC821 4.3 (and RFC2821
4.3.1). Note that the hostname given in the SMTP greeting should have an A
record pointing back to the same server. Note that this one test may use a
cached DNS record.
smtp.secureserver.net claims to be host
pre-smtp15-02.prod.mesa1.secureserver.net [but that host is at 64.202.166.68
(may be cached), not 64.202.166.12].
mailstore1.secureserver.net claims to be host
pre-smtp24-01.prod.mesa1.secureserver.net [but that host is at 64.202.166.84
(may be cached), not 64.202.166.11].
-------
There is currently -no- way of reaching your SBServer without explicitly
knowing your public IP Address.
You have a bit of cleaning up and work to do.
--
Henry Craven {SBS-MVP}
"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DDCF536E-52B8-4514-B0C1-0DA9E5C7610B@xxxxxxxxxxxxxxxx
> Hi All,
>
> I have setup a new Windows 2003 SBS server . when i go to the client
> machine
> and type the servers IP Address i get the Remote Web work place . > However
> when i try to access the machine through internet i am not able to get > RWW
>
> My setting is like this
>
> I have two LAN CARDS . one for my server with IP (192.168.0.61) and one
> for
> my ASDL broadband with IP (usually 192.168.1.1 .. asssigned by the ISP
> DHCP )
>
> my Website is hosted with Godaddy.com and the domain name is > www.kvco.in .
> But When i installed windows 2003 SBS , i have given with extn > kvco.local
> to avoid conflict with my above DNS . However in SBS setup i have > noticed
> that the RWW Web address is Https://www.kvco.in/remote . so how do i > set
> this
> up . Do i need to buy a static ip . Do i need to copy some file to my
> Webhosting ISP .
>
> Is there any information which can give a complete picture
>
> Thanks
.
- References:
- Prev by Date: Re: OWA Loading Issue
- Next by Date: Re: Branch Office Architecture
- Previous by thread: Re: Setting up Remote Web work place to acess from Internet
- Next by thread: Re: Allow user access to member server by way of Remote Web Workplace
- Index(es):
Relevant Pages
|
