re: Server *unreachable* outside of local network
Friday, January 13, 2006 at 3:47 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by Curt R
(773 messages posted)
Well, I have to say your setup is a little odd. If it were me setting things
up, I would have the internet coming in to the firewalled router and from there into
the switch into which all servers and clients would be plugged.
example:
internet
>> router >> switch >> clients & servers.M
The way you have things setup now,
all your servers are in front of your firewall which makes no sense...they should
be behind the firewall with possibly the exception of the web server which could
be in a DMZ. If 2003 is your LAN's DNS server, you should be forwarding it's DNS
to your ISP's DNS for resolution of requests outside the local zone. To allow external
users to connect to your website, you would forward port 80 to your web servers IP
address. A couple questions I have for you: If your present DNS server is your
2003 server, what is the secondary DNS server (ie: 66...) and where is it located
and how does it figure into your network? Being as how it's on a different network,
it's no surprise nobody on the 64 network can ping it....it is on a different
network. Are you running an Active Directory integrated domain with the 2003 server
as your DC?
On Friday, January 13, 2006 at 11:37 am, Evan K wrote:
>We have a local network consisting of several linux servers, an old WinNT server,
>a new Win2k3 and several workstations. The internet connection comes in to a switch,
>which branches off to the servers directly, and to a firewalled router. The router
>then branches off to any workstations.
>
>For some reason, IIS, WMS, and Windows file sharing from the 2k3 server works fine
>when accessed from the NT server, most of the linux servers, or any of the workstations,
>but NOTHING on 2k3 is accessible outside of the switch. The DNS is resolving ('2k3.ourdomain.com'
>resolves to 2k3's static ip '64.xxx.xxx.xx'). The TCP/IP properties of its network
>connection are like so:
>
>(X) Use the following IP address
>IP address: 64.xxx.xxx.xx
>Subnet mask: 255.0.0.0
>Default gateway: (blank)
>
>(X) Use the following DNS server addresses
>Preferred DNS server: 64.xxx.xxx.xx
>Alternate DNS server: 66.xxx.xxx.xx
>
>Now, any of our servers with a 64.xxx.xxx.xx ip (and workstations) can access the
>2k3 server fine, but nothing else (including our secondary dns server, 66.xxx.xxx.xx)
>gets a response, even from a ping.
>
>Windows Firewall is disabled, as is ICS. If we were to enable ICS, windows prompts
>us that it will *change* its ip to 192.168.0.1, which would conflict with our router.
> We dont want 2k3 to be the hub of our network, we just want it to act as webserver/media
>server to the outside world (which it doesnt want to do) and file server/accounting
>server on our local SMB network (which it IS currently doing).
>
>is there something we've just missed?
|
All messages in this thread [show all]
 |  | re: Server *unreachable* outside of local network (Curt R: Fri, Jan 13, 2006, 3:47 pm) |
|
