Re: Please help me as I am clueless at this point!

Tech-Archive recommends: Fix windows errors by optimizing your registry

I am a little confused by your configuration. Your 1st post says Netgear
router and this one says Linksys. In anycase your DNS is Wrong. The DNS for
ALL computers on the Network must point to the SBS NIC. I suggest a second
NIC configured like the example at
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
but if you stick to a single NIC then disable DHCP on the router and enable
DHCP on SBS so that the Clints will get their IP and DNS from SBS.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"jlab13" <johnlab13@xxxxxxxxx> wrote in message
news:1150042062.238021.213550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Server:
Windows IP Config:

Hostname...............................................blahserver
Primary Dns Suffix.................................blahcompany.local
Node Type..............................................Unknown
IP Routing Enabled.................................Yes
Wins Proxy Enabled...............................Yes
DNS Suffix Search List...........................blahcompany.local

Ethernet adaptor Server Local Area Connection

Connection-specific DNS Suffix . :
Description.............................................Realtek
RTL8139 Fast Ethernet NIC
Physical
Address...................................00-11-D8-73-E4-B9
DCHP Enabled.......................................No
IP
Address..............................................192.168.0.101
Subnet Mask...........................................255.255.255.0
Defaualt Gateway....................................192.168.0.1
DNS Servers...........................................192.168.0.101
Primary Wins Server...............................192.168.0.101



Client:

Windows IP Config

Host Name.................................................Desktop
Primary Dns Suffix.....................................:
Node Type..................................................Unknown
IP Routing Enabled.....................................No
Wins Proxy Enabled...................................No


Ethernet adaptor Local Area Connection

Connection Specific DNS Suffix..................:

Description...................................................NVidia
Net Controller
Physical
Address.........................................00-11-D8-8A-1f-B2
DCHP Enabled.............................................Yes
Autoconfiguration Enabled............................Yes
IP
Address....................................................192.168.1.100
Subnet
Mask.................................................255.255.255.0
Default
Gateway...........................................192.168.1.1
DHCP
Server................................................192.168.1.1
DNS
Servers.................................................205.152.37.23

205.152.144.23
Lease Obtained.............................................6/11/06
10:39:44 am
Lease
Expires................................................6/12/06 10:39:44
am




fwiw

The client is an XP Pro sp 2 system running through a basic linksys+dsl
modem.









Frank McCallister SBS MVP wrote:
Please Post the output from IPCONFIG /ALL from your server and one WS

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"jlab13" <johnlab13@xxxxxxxxx> wrote in message
news:1150033484.739342.131080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I appreciate all of the posts.

We are aware that the full functionality of termianla services is not
aorund in SBS standard. Since it's just 2 of us, we were just going to
use it as a means to connect to this one program via remote desktop
connection on xp.

So can anyone expound on the "ConnectComputer" problem? I am working my
way down the "to do" list, and this is where I'm at.
Thx

Leythos wrote:
In article <1150000644.326859.30250@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
johnlab13@xxxxxxxxx says...
I am about a week and a half deep into SBS Standard 2003 at my
office.
The goal is to get my branch in ATL and my partners branch in New
Orleans to share this database program the 2 of use. The program
maker
has told us it works best using Terminal Server.

Terminal Services requires a second server, SBS2003 does not permit
configuring itself to run applications in Terminal Service Mode for
users.

The other option would be to have a local computer running Remote
Desktop or VNC

The problem is, I can't seem to get newly created users/computers
configured correctly. I'm using an external DLink router to handle
dhcp
as I'm to clueless to try to set it up on sbs right now. I get
through
the whole "add user/client computer" stage up until I get to the
window
that pops up and says "goto '\\server\ConnectComputer'. When I do
this
on a connected client at the office, I enter my user and pass and
get
the error:

You can not use a different DHCP service - you MUST configure SBS2003
for DHCP and DNS in order to make your life simple.

All computers must point to the SBS server for DNS, the DHCP service
should be configured to issue the values needed to each clinet PC.

"The list of users and computers cannot be found.Make sure the
client
computer has a wired connection (paraphrasing)If you have a router
controlling DHCP, make sure the computer running sbs is set to be
the
primary DNS."
----It is, at the reserved ip of 192.168.0.101

101? 101 sounds like a dynamic IP issued by your router.

When I try to get through this stage from home on a client
computer,I
get:

"You are not authorized to view this page.
HTTP Error 403.6 - Forbidden: IP address of the client has
been rejected.
Internet Information Services (IIS)"

You can not access the 192.168.0.101 address from home, you have to
access using the public IP address and your router should be
configured
to forward TCP80>192.168.0.101.

I have all IP's allowed right now in IIS, so I have no idea where
this
is coming from.

Any ideas would be welcome. All I' need in life is to get this thing
working where 2 people can log into terminal server to use one
program.

Your entire concept of SBS is wrong, there is no TS in SBS unless you
purchase a second server to run TS on. The best you can do is setup RD
on a local workstation to allow the remote users to access it.


--

spam999free@xxxxxxxxxx
remove 999 in order to email me




.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... Les Connor [SBS Community Member - SBS MVP] ... No DNS Name Resolution If DHCP Client Service Is Not Running ... You have a full-time broadband connection. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Go back to pointing the external NIC DNS Servers to the SBS server IP ... make sure the DHCP Client Service is running on the server. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... In the TCP/IP properties for the external NIC, you need to specify an external DNS server for DNS, instead of the server's own IP address. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW Network Error
    ... both NICs on SBS should get DNS from the 'internal' SBS NIC. ... The SBS DNS Server service can then be told to use the router or your ISP's DNS Servers as forwarderby submitting such during the CEICW or manual adjustment, OR you can leave the DNS setting blank during CEICW and SBS DNS will resolve using 'root hints'. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Merv Porter [SBS MVP] ... dish that I have currently plugged into the router. ... IP it means that your problem is now DNS. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)