Windows Server 2003 help

I

iOprah

Thread Thumper
Joined
Sep 8, 2008
Messages
1,142
Hello,


I am currently trying to setup a windows 2003 for small business server on a Dell PE830. The server is connected to a At&t Uverse router, and has an assigned static ip. The server connects to the internet and can connect to the server start page(which is assessable via the servers ip.). The server used to be connected somewhere else and the start page was able to be connected to from any computer connected to the internet, by typing the servers ip address. Now I can't connect to it, either on the local network or anywhere else. I also cannot ping the server it always says connection timed out, I am however able to access the server remotely via "log me in".I need this server connected because it runs software that enables files (mortgage files) to be shared amoung Mortgage Processors and loan officers. It is called encompass. Also whats weird, when I attempt to connect to the ip it loads and takes about 2 minutes to say "this page cannot be displayed" where as if I type any other ip address is immediately tell me "this page cannot be displayed.
Please help i spent all day doing this and cannot get it to work.

Thanks,
Oprah

P.s. Feel free to ask any questions.
 
Last edited:
In order for it to work remotely from behind a router, you'll need to forward a couple of ports (depending on the services you're running).

Here are some common services and the ports that you'd have to forward for them to work properly:
Port 21 TCP: FTP (Additional ranges required)
Port 53 TCP/UDP: DNS
Port 80 TCP: Web (HTTP)
Port 443 TCP: Web (HTTPS)
Port 3389 TCP: Remote Desktop (RDP)

You most likely only need to forward port 80 to access the server's start page though. Also, keep in mind that most consumer-level routers do not support NAT reflection, so you probably won't be able to access your server locally using your external IP address.
 
Have you recently made any changes to the setup (ie, have you changed anything with the router, changed anything with your connection...)?
Is your router set up with ip forwarding or a dmz to make the server accessible from the outside?
Is the computer's firewall engaged, and at what setting if it is?
Check your router's WAN ip address, is it the same as what it used to be?
 
AT&T routers are usually pretty decent about automatically creating loopback NAT policies based on your inbound ones. I seriously doubt you need to forward 53 to your server. I've only had to do that about three times ever, and that's because I was doing a DNS based whitelist for a retail company.

gothroach said:
In order for it to work remotely from behind a router, you'll need to forward a couple of ports (depending on the services you're running).

Here are some common services and the ports that you'd have to forward for them to work properly:
Port 21 TCP: FTP (Additional ranges required)
Port 53 TCP/UDP: DNS
Port 80 TCP: Web (HTTP)
Port 443 TCP: Web (HTTPS)
Port 3389 TCP: Remote Desktop (RDP)

You most likely only need to forward port 80 to access the server's start page though. Also, keep in mind that most consumer-level routers do not support NAT reflection, so you probably won't be able to access your server locally using your external IP address.
Click to expand...
 
BFM said:
AT&T routers are usually pretty decent about automatically creating loopback NAT policies based on your inbound ones. I seriously doubt you need to forward 53 to your server. I've only had to do that about three times ever, and that's because I was doing a DNS based whitelist for a retail company.
Click to expand...

I'm used to doing port 53 with retail customers for AD, though it doesn't sound like they're running it.
 
I moved the router to my house, and I am now using a Westell Versalink Router from bellsouth (At&T). It still is getting the same problem. It is still not connectible from other computers, However if you type the ip address on the server itself it can get to the start page and can connect to the encompass software while in networked mode. One thing that i should add, the ip address at both locations (the office where it was set-up with uverse(att) and at my house) was not able to be pinged always getting connection timed out. On my router it is in Ip passthrough mode, and all ports 80-1723 are open on both tcp and udp. The firewall is off and dhcp is enabled. The server is also connected in auto mode, its getting the ip address and dns are automatically configured from the server.


-
 
Last edited:
You must log in or register to reply here.

Latest posts

Back
Top