Stu V
Guest
|
 Posted:
Wed Jan 19, 2005 5:03 pm Post subject:
Expanding the basic install |
|
|
Hi, I have just installed SBS 2003 pretty much out of the box, and generally
it is running along fine. I have a small issue in that I have a third nic in
my server - which I configured on its own subnet, and i run my office Wired
network on one nic, and a wireless AP on the other providing wireless comms
to the office. The wireless comms connection is the new nic. (The third nic
is my "DMZ" connection.)
I can connect to the AP using a wireless device, and get web access, so i
know my RRAS and DNS are working ok, I can also ping the three interfaces of
the server, however if I try to join the domain, or run up the mycompanyweb
website on the server, it breaks. The joining domain function simply says
that a DC is not available.
I have added the additional subnet in my AD sites and services, what else do
I need to do to let the server know that this nic / subnet is on its internal
(trusted) network?
Regards
stu V |
|
daniel
Guest
|
| Posted:
Wed Jan 19, 2005 11:15 pm Post subject:
Re: Expanding the basic install |
|
|
This seems an odd setup to me. If I had to have a wireless gateway, I would
use a wireless access point wired back to my network switch.
If you are trying to offer domain services to the wireless subnet, how is
this a DMZ?
Correct me if I'm wrong but I think the only thing you'll end up separating
are the wired and wireless clients.
"Stu V" <Stu V@discussions.microsoft.com> wrote in message
news:A53A236C-C9BF-46A9-A53F-F8314D5EED8D@microsoft.com...
| Quote: | Hi, I have just installed SBS 2003 pretty much out of the box, and
generally
it is running along fine. I have a small issue in that I have a third nic
in
my server - which I configured on its own subnet, and i run my office
Wired
network on one nic, and a wireless AP on the other providing wireless
comms
to the office. The wireless comms connection is the new nic. (The third
nic
is my "DMZ" connection.)
I can connect to the AP using a wireless device, and get web access, so i
know my RRAS and DNS are working ok, I can also ping the three interfaces
of
the server, however if I try to join the domain, or run up the
mycompanyweb
website on the server, it breaks. The joining domain function simply says
that a DC is not available.
I have added the additional subnet in my AD sites and services, what else
do
I need to do to let the server know that this nic / subnet is on its
internal
(trusted) network?
Regards
stu V |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in