Server *unreachable* outside of local network
Friday, January 13, 2006 at 11:37 am
Windows Server 2003 Annoyances Discussion Forum
Posted by Evan K
(9 messages posted)
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?
|
Responses to this message:
|
|
All messages in this thread [show all]
 | Server *unreachable* outside of local network (Evan K: Fri, Jan 13, 2006, 11:37 am) |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
