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

Tech-Archive recommends: Speed Up your PC by fixing your registry



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

  • ISA Array and NLB fail to work properly.
    ... I am trying to setup an array with two nodes clustered via NLB for fault tolerance and load balancing. ... I want clients configured with a single proxy address to use either of the two ISA machines, depending on load and availability, without requiring reconfiguration of the client's proxy configuration. ... When the clients are configured to use NodeA as the proxy, they are able to access the internet. ...
    (microsoft.public.isa.enterprise)
  • RE: Network configuration
    ... I'll include my configuration here for others in the same situation (any ... xl1 and xl0 are bridged so that all clients have full internet connectivity. ... > Subject: RE: Network configuration ...
    (freebsd-questions)
  • Re: Name Resolution and Win98 Clients
    ... Add the sbs2k's internal IP address as the WINS server in the 98's network ... configuration. ... > logged and Internet access failures. ... > names would resolve on any of the Win98 clients. ...
    (microsoft.public.backoffice.smallbiz2000)
  • ipsec and NAT
    ... I have the following configuration: ... I can ping from the clients to the gateway, ... I CANNOT ping from the clients to the internet ...
    (comp.os.linux.networking)
  • Re: iptables: port forwarding and hardware router
    ... > I have the following configuration: ... > With this settings, everything works fine, all clients can send and ... > data from the internet. ... SWITCH (Check to see if the uplink being used to send the data to eth0? ...
    (alt.os.linux.suse)