Re: Remote Web Desktop Connection - DHCP scope

Hi again,

This is an adendum to the one below. I have uploaded screen shots of my
latest configuration at www.mvanert.com. With this configuration I am able to
ping the server and the isp dns as well as access the 'net. However, none of
the workgroup computers can access the internet through the server. From a
workgroup computer I can ping 192.168.16.2 but not the router 192.168.1.1 see
the last image on my site for details of workgroup nic.

Where have I gone wrong please?

Michael
--
mvanert


"Michael Van Ert" wrote:

Hi Anna,

I've gone through the setup as outlined and have configured the router and
nics as indicated.

I get to the point where I ping the router and that goes great, can ping all
day long. However, trying to ping the isp dns 154.11.128.59 goes nowhere.
And, of course, there is no connection to the net.

I have a couple of questions, when setting up the two nics, I have not
included a default gateway or dns server addresses in either. Another
question, when setting this up I have both the DHCP and DNS services turned
off, am I screwing up here? The reason I did this is I could not get CEICW to
work without turning them off.

Once again your assistance is greatly appreciated.

Regards,
Michael

--
mvanert


"Anna Clark" wrote:

Hi Michael:

Please correct anything below that is incorrect:

1. Your isp has given you the following static ip info for the public
facing side of your router:
IP 154.5.127.137
SNM 255.255.254.0
DGW 154.5.126.254
DNS 154.11.128.59
DNS 154.11.128.187

2. your local router setting for the local, LAN, facing side of your
router is
192.168.1.1
255.255.255.0

2. Your server1 nic is set for a static ip. The MS suggested one is:
IP: 192.168.16.2
SN 255.255.255.0
nothing else goes here

3 Your server2 nic is set for a static ip. The range that matches your
router is:
IP 192.168.1.xxx could be any number between 2 and 254. I
usually use the same last number as server1 nic
SN 255.255.255.0 must match the subnet of the router

The server1 nic is plugged into your switch,
The server2 nic is plugged into your router.

The wan device is plugged into the wan port on your router.

You should change the setting "gateway" to "router" on the first page of
your router.

When all this is done, and the little lights by the cable port connections
are lit to indicate that you have good connections you should be able to
open a cmd prompt on the server and issue the command:

"ping 192.168.1.1", and get a reply response from your router.

Now, run the CEICW: put the address for DNS that the ISP gave you in there,
and be sure that the ip addresses are correct as above.

After the CEICW finishes, you should be able to issue the following two
commands

ping 192.168.1.1 to hit your router

ping 154.11.128.59 to hit the ip address of the isp dns server.

If you can do that, your browser on your server should find the internet.
Don't do much from there... bad form.

Now, turn on DHCP on the server, set the scope to contain enough static ip
addresses to cover however many servers and ip printers you may need. The
default is 10.

Have you added the users and computers and joined them to the server? If
not, and the above is working, post a new thread for assistance if you need
some.

Post back if not clear.

--
Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.



"Michael Van Ert" <MichaelVanErt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:848C7D90-0529-4CFA-806A-857D065E2D8B@xxxxxxxxxxxxxxxx
Hi Anna,

Sorry for the delay, I can only get to work on the server on Saturdays. I
tried putting a second nic in and to follow your instructions. I could not
get the workgroup computers to access the internet.

Here's what I've done, I've unplugged the second nic, and the system is
wired like this: ISP>Router>Switch & SBS so that both the workgroup and
sbs
domain can access the internet & sbs can access its' lone workstation.

I've put all the router settings on my web site www.mvanert.com under the
link SBS 2003 link so that you can see the way the router and nic are set
and
I'm hoping this will help you talk to me in a way I understand with the
hardware I'm using.

I really appreciate your help.

Michael Van Ert
--
mvanert


"Anna Clark" wrote:

Hi Michael:

Ok, more clear now.

How many travelers?

With the setup you have now, you can take over the one XP pro
workstation
when you connect with RWW and work on your Access DB on that desktop.
But
only one at a time, and only when it is not being used locally.

SBS does not allow TS in app share mode,, only for admin purposes.

If the final goal is several travelers, you will need one workstation
for
each remote connection, or a separate box with TS.
RWW with out TS is one to one. With TS is many to one.

--
Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.



"Michael Van Ert" <MichaelVanErt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D8DB38FC-A5C3-40E8-B69A-8DACC7DEB0AC@xxxxxxxxxxxxxxxx
First, thank you Anna for your response.

To answer your questions:

8 workstations are legacy, the SBS was purchased for this one project
only.
We are a very small non-profit (read no money) and were led to believe
this
was the way to go. These will be replaced and configured to join the
domain
as $ permit.

1 XP Pro workstation is to host the MSAccess file / domain.

SBS standard - see above, to be able to access and manipulate this
file
from
anywhere.

I will implement according to your instructions and get back here in
the
next two days (I have two jobs, so it takes a day or so to get at the
server)

Once again, thanks.
--
mvanert


"Anna Clark" wrote:

Hi Michael:

8 workstations, MS XP Home, peer to peer. What purpose?

1 MS XP Pro Workstation. What purpose?

SBS 2003 Standard(?). What purpose?

Goal - run MS Access from anywhere in the world.

If this is your only goal, install Windows Server 2003, not SBS.

Add the Terminal Server Role

Install MS Office according to instructions for installing on a
Terminal
Server.

Purchase TS licenses for the correct number of remote users.

Connect to the TS from anywhere in the world and run Access, or any
Terminal
Server compatible program.

If you have other goals, you may get better/additional advice if you
tell us
what they are.

Regardless of SBS or TS:

Workstations->Switch->Server
Server->Router->Wan Device

Configure router with the IP your ISP gave you, then open ports on
Router,
forward to NIC in Server.

With SBS you want two NIC's, and two subnets, unless you have
industrial
strength Firewall between Server and Wan Device. Also with SBS you
should
allow the SBS to service DHCP to its client workstations, configure
the
router with the settings from the ISP, and run the CEICW. Any
computer
that
relies on SBS for its services, including the SBS, must have ONLY
the
internal NIC in the SBS as its DNS setting, i.e. 192.168.1.50,

The only place those other number appear is on the WAN facing side
of
your
router and in the DNS forwarders tab.

--
Regards:

Anna Clark
-----
Please do post the conclusion or solution
to your issue so that others may benefit.



"Michael Van Ert" <MichaelVanErt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:FC134F19-DB82-448A-B3B6-DB98BEABD928@xxxxxxxxxxxxxxxx
First, thanks to those who have responded. Out of sheer fustration
I've
re-set my router to default, turned off DHCP in SBS 2003. Here's
my
current
configuration (I need to start from scratch):

ISP>Router>Switch>Server & 8 workstations running XP Home,
peer-to-peer 1
workstation running XP Pro to be attached to domain CPSports

Goal: to be able to work with MSAccess file using remote desktop
from
anywhere in the world.

The router (Linksys WRT54G ver. 6) is configured thusly:
Auto DHCP
Host=Sportability (which is linked to an IP of 154.5.127.137)
Domain=cpsports
MTU=auto
Local IP=192.168.1.1
Starting IP=192.168.1.100
50 DHCP users max
Static DNS 1: 154.11.128.59
DNS2: 154.11.128.187
------
Server Name is cpserver
domain=CPSports.local
Server IP=192.168.1.50

Regards,
Michael
--
mvanert


"Anna Clark" wrote:

Hi Michael:

.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... laptop plugged into port on DSL router. ... service, e-mail, and RWW is available to all users on the network. ... The server is a SBS2003 SP1 Standard box without ISA, ... of the two NICs by clicking the Advanced tabs, it won't open that box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... The server is a SBS2003 SP1 Standard box without ISA, ... the two NICs by clicking the Advanced tabs, it won't open that box, and ... program or service is running that might use the network address translation ... Is the Modem also your Router? ...
    (microsoft.public.windows.server.sbs)