Re: SBS 2003 no access to internal interface after adding NAT/basi

You don't have anything close to a standard SBS 2003 setup-just because you
have 2 NICs doesn't make it so with both NICs on the same subnet connected
to the same switch. Its doubtful you'll get it to work (how it did
originally is a real mystery). As Cris says at least simplify things to 1
NIC at this point and then take a close look at what you need to do to
actually use 2 NICs and then make use of the CEICW as SBS 2003 was designed
to do. Just make sure you have a good external firewall while running with 1
NIC.

"My Name" <MyName@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A0AB202-3AE7-4566-834C-9F7A027BE45D@xxxxxxxxxxxxxxxx
Hi Cris,

well, we are kind of part of a company but the structure is decentralized.

Both nics connect to the same switch. No, we haven't considered switching
to
one nic because the standard setting in sbs 2003 is having two nics and we
don't want to make the system "more unusual".

Anyway, it has been working until nat/basic firewall was deleted.

Thank you very much for your help in advance!

Lars




"Cris Hanna" wrote:

Additionally what are both nics connecting to?
Have you considered switching to one nic...might be easier and better
supported than two in the same subnet

--
CRIS HANNA [SBS-MVP]
---------------------------------
Please only respond in the newsgroup. Do Not Contact Directly.
MVPs do not work for Microsoft.
---------------------------------------
Sent via Windows Mail on Vista Ultimate connected to SBS R2
"My Name" <MyName@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C9824699-5953-4E52-B305-FC9298F3F452@xxxxxxxxxxxxxxxx
Dear Cris,

thanks for replying. Well, we know this setting (routable addresses,
two
nics in the same subnet) is a bit unusual but it worked before. We even
know
that the internal nic is accessible from the internet (in this kind of
setting). Because of certain policy reason in our company we have to
configure it that way. By now, we can't change this setting.

What we did:

1. everything worked except the access to internal nic from the
internet
2. nat/basic firewall was deleted -> access to internal nic (external
clients), but no access from internal clients to the internet (although
access to internal nic)
3. nat/basic firewall was added -> access to the internet (internal
clients), but no access to internal nic, external clients have no
access
to
internal nic
4. deleting the 'network connection' in nat/basic firewall allows
internal
clients to access the internal nic, but no access to the internet
5. deleting the 'lan connection' is the other way round. internet
access,
but now access to internal nic (internal clients)

'internet and mail configuration' doesn't solve this problem. So, we
think
some extra settings must have been deleted when nat/basic firewall was
removed.

Thank you very much for your help in advance.

Kind regards,
Lars






3.





"Cris Hanna" wrote:

well your first paragraph where you mention your config is the problem
With internal and external nics on the same subnet...you have two
internal
nics...it just won't work
And why do clients have routeable addresses

You'd have to come up with some very compelling explanations for what
you've
done before going forward with a solution.

--
CRIS HANNA [SBS-MVP]
---------------------------------
Please only respond in the newsgroup. Do Not Contact Directly.
MVPs do not work for Microsoft.
---------------------------------------
Sent via Windows Mail on Vista Ultimate connected to SBS R2
"My Name" <My Name@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DBC9C553-7BE2-44DE-84A9-5FB727CCB8F2@xxxxxxxxxxxxxxxx
Hi,

we got the following problem:

configuration: SBS 2003, Windows XP Clients (SP2), clients have
routable
IP-Addresses, internal and external interface of the server are in
same
subnet (only this configuration was feasible due to internal
circumstances)

Clients had access to the internal interface of the sbs 2003 (and
internet
access) until yesterday. "Only" external clients weren't allowed to
access
the internal interface of sbs 2003. To resolve his problem we were
adviced
to
delete the interface "NAT/basic firewall" in "Routing and RAS".
After
this
we
had access to the internal interface from external PCs. But local
clients
didn't have access to the internet any more. So, the interface
"NAT/Basic
firewall" was added again. Local clients now have access to the
internet
but
can't access the internal interface (owa, etc.) The server though
can
accessing the internet.

Unfortunately, accessing the interal interface from "outside" (the
first
problem) isn't possible.

Thank you for your help!





.

Relevant Pages

  • Re: After installing SBS 2003 two IE 6.0.29 SP2 clients that cannot to companyweb
    ... Mozilla, and other clients can access the http://comanyweb, the SBS server ... Reset the Internet Explorer Settings to Default. ... DHCP was turned off in SBS 2003. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I configure SBS 2003 as a DHCP server?
    ... Knowledgeable SBS MVPs and others of us have tried hard to help you, ... I don't like the idea of a router between SBS and my modem. ... My network now consists of the modem at the edge facing the Internet. ... > post) for the server indicated that you have 2 NICS and that the ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2000 clinet cannot ping Public IP
    ... You can not use multiple gateways in SBS internal clients. ... This newsgroup only focuses on SBS technical issues. ... |> internet IP from client computer. ...
    (microsoft.public.windows.server.sbs)
  • Re: Boot-up question on SBS2K3
    ... SBS External NIC ... The router separates you from the Internet. ... >>> 2 Nics, broadband cable modem connected into the external NIC, internal ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting Clients to SBS server - First time
    ... reconfigure your SBS External interface to talk to it (ie. ... ISA) router to look after the internet connection. ... > switch as the SBS server is a Netware server with IP of 192.168.1.2. ... >> It looks like you have 2 NICs and a router for your network topology. ...
    (microsoft.public.windows.server.sbs)