Computing.Net > Forums > Windows Server 2003 > Resolving to hostname

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Resolving to hostname

Reply to Message Icon

Name: vladimirt
Date: November 23, 2008 at 16:15:22 Pacific
OS: win2003 server
CPU/Ram: athlon3k+ 2gb
Comment:

Hi,

I have a Project Server 2007 set up on Windows server 2003 (without DNS), which works well in local area network. Hostname of Windows server is WINSERVER.

Now I want to enable access to project web access from Internet, so I have forwarded the required port on my router to local IP address of windows
server.

When I type in URL like http://my_public_IP_address:port/PWA, it gets
resolved to http://WINSERVER:port/PWA - which of course won't work from anywhere else then my local network.

Is there any way to stop that kind of name resolution, and just forward that port to windows server? I'm using IIS 6.0.

Best regards.
Vladimir



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: November 24, 2008 at 06:42:24 Pacific
Reply:

Normally with a port forward you are pointing the forward at a specific IP on your LAN. So I'm wondering why you use the following command to try to connect remotely:

<a href="http://my_public_IP_address:port/PWA</B>" target="_blank">http://my_public_IP_address:port/PW...

Try this without anything but the public IP of your external connection.

I think you're adding in a port number when it's not required. Think about it, on your router you've set up a port forward. So, when a connection comes in from say, http, it knows to send port 80 to the specified IP address on your LAN.

I'm not familiar with the software you're using but I've set up port forwards for RDC and SSH at home and when I wish to connect, I just use the external IP.

If I'm connecting with SSH, my router sends it to my UNIX box. If I'm using RDC, it sends it to my XP PC.


0

Response Number 2
Name: vladimirt
Date: November 24, 2008 at 08:44:23 Pacific
Reply:

Hello, I can't remove port number, since port forwarding on router is set to forward all traffic on my custom port (say 8080) to the same port (8080) on a local computer with privet IP address. I'm already using default http port (80) for other things.

Bottom line is that the traffic is correctly forwarded to windows server, but when it arrives URL is somehow rewritten to incorrect format. I have other ports forwarded to Linux box, which work like a charm, so my guess is that something is wrong in Windows server configuration, probbably IIS.

Best regards,
Vladimir


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Resolving to hostname

dns resolves to powweb www.computing.net/answers/windows-2003/dns-resolves-to-powweb/8640.html

hostnames resolvin to external ip www.computing.net/answers/windows-2003/hostnames-resolvin-to-external-ip/8607.html

Getting S2003 DNS to prefer an IP www.computing.net/answers/windows-2003/getting-s2003-dns-to-prefer-an-ip/5020.html