Problem with IIS 6.0 and multiple IP Addresses

[GaryK]

Last night I added a new IP Address to IIS6 on my Windows 2003 Server.

The default website is set to All Unassigned IP Addresses.

The new website has the actual IP Address selected.

During the testing phase I want to access the new site by IP Address only.

When I try to use HTTP or FTP to access the site via IP Address though my attempts time-out.

A tracert shows the IP as resolving to www.garykeith.com which is correct and suggests to me everything is setup correctly at SB.

There are no entries in my firewall logs to indicate a connection is even being attempted.

Any ideas on what might be wrong?

Thanks,
~gary.

[GaryK]

Sorry to double post but the time to edit my last message has expired.

I wanted to add that I missed something the first time I did a TraceRt to the IP Address in question.

What I missed is the request doesn't seem to make it past one of ServerBeach's routers at 69.44.56.67.

[DXD]

Did you just get the new IP address from ServerBeach?

Sounds like they did not add it to their routing at their router you may want to open a trouble ticket for that new ip address.

[GaryK]

Thanks for your reply.

I was assigned the IP Address on October 2nd, but didn't get around to installing it until last night.

I tried to open a report ticket under IP Addresses/Troubleshooting but it required one ticket and it didn't seem right that I had to pay (use one ticket) to fix a problem I didn't cause.

So instead I reported it as a network problem which didn't cost me a ticket. And it does seem more like a network problem than an IP Address troubleshooting problem.

[KyleMulligan]

Post the entire tracert output. That'll shed some light on the issue. The fact that it resolves www.garykeith.com doesn't automatically mean that it is being routed properly. It just means it has the proper PTR record in ServerBeach's nameservers.

[GaryK]

Hi Kyle.

The final IP Address in the first tracert is a SB router. Normally the next hop would be to my server as it is in the second tracert.

Thanks.

Tracing route to www.garykeith.com [69.44.159.54]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 14 ms 12 ms 12 ms 65.14.252.9
3 14 ms 16 ms 18 ms 65.14.255.49
4 15 ms 25 ms 29 ms 205.152.145.177
5 13 ms 52 ms 13 ms axr00mia-1-3-0.bellsouth.net [65.83.237.8]
6 14 ms 14 ms 14 ms pxr00mia-2-0-0.bellsouth.net [65.83.236.18]
7 29 ms 29 ms 30 ms so-0-1-0-0.gar1.Miami1.Level3.net [65.57.174.5]
8 29 ms 28 ms 29 ms so-7-0-0.mp2.Miami1.Level3.net [4.68.112.45]
9 46 ms 46 ms 45 ms ae-0-0.bbr2.Washington1.Level3.net [64.159.0.230]
10 45 ms 45 ms 45 ms so-7-0-0.edge1.Washington1.Level3.net [209.244.11.14]
11 46 ms 47 ms 46 ms cpr2-gigabitethernet3-2.VirginiaEquinix.savvis.net [208.173.52.77]
12 45 ms 45 ms 44 ms cpr1-ge-2-0.VirginiaEquinix.savvis.net [206.24.227.45]
13 50 ms 49 ms 49 ms peer-1-networks.VirginiaEquinix.savvis.net [208.173.10.150]
14 43 ms 42 ms 42 ms 216.187.115.250
15 44 ms 43 ms 44 ms 69.44.56.67
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to blazertech.com [69.44.152.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 12 ms * 65.14.252.9
3 13 ms 13 ms 13 ms 65.14.255.49
4 14 ms 14 ms 13 ms 205.152.145.177
5 13 ms 14 ms 14 ms axr00mia-1-3-1.bellsouth.net [65.83.237.10]
6 29 ms 13 ms 15 ms pxr00mia-2-0-0.bellsouth.net [65.83.236.18]
7 34 ms 29 ms 29 ms so-0-1-0-0.gar1.Miami1.Level3.net [65.57.174.5]
8 30 ms 30 ms 75 ms so-7-0-0.mp2.Miami1.Level3.net [4.68.112.45]
9 45 ms 45 ms 45 ms ae-0-0.bbr2.Washington1.Level3.net [64.159.0.230]
10 45 ms 93 ms 46 ms so-6-0-0.edge1.Washington1.Level3.net [209.244.11.10]
11 46 ms 46 ms 46 ms cpr2-gigabitethernet2-2.VirginiaEquinix.savvis.net [208.173.52.73]
12 46 ms 46 ms 46 ms cpr1-ge-2-1.VirginiaEquinix.savvis.net [206.24.227.49]
13 48 ms 49 ms 49 ms peer-1-networks.VirginiaEquinix.savvis.net [208.173.10.150]
14 43 ms 42 ms 42 ms 216.187.115.250
15 43 ms 44 ms 44 ms 69.44.56.67
16 44 ms 44 ms 43 ms blazertech.com [69.44.152.200]

Trace complete.

[GaryK]

SB still has not responded to my ticket. Their customer support is really very bad. I've been trying for two months to get a billing issue resolved without success.

Anyway, I learned a little while ago this seems to be a problem that's unique to me.

Out of desperation I contacted the folks at Kerio to make sure their new firewall product supports multiple IP Addresses. I was sure the answer would be yes but as I stated, I was desperate. In the process they asked for my new IP Address and were able to see the website that's there.

So now I'm wondering why I can't see it.

If it were a DNS problem with my ISP I wouldn't expect the IP Address to resolve to the correct domain name and yet it does even though I can't access the website itself.

I'm completely out of ideas right now. Maybe I need some more caffeine? Any suggestions would be appreciated.

[KyleMulligan]

It does look like a routing issue, but it seems to be related to the route you take to get to SB's network. I can complete the tracert just fine:
C:\Documents and Settings\kmulliga>tracert 69.44.159.54

Tracing route to www.garykeith.com [69.44.159.54]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.253
2 9 ms 23 ms 7 ms 10.100.240.1
3 10 ms 11 ms 12 ms 68.13.8.145
4 10 ms 10 ms 11 ms 68.13.8.21
5 11 ms * 8 ms mtc1dsrc01-gew0304.rd.om.cox.net [68.13.14.9]
6 10 ms 11 ms 11 ms mtc1bbrc01-pos0101.rd.om.cox.net [68.1.0.124]
7 36 ms 22 ms 11 ms mtc1bbrc02-pos0100.rd.om.cox.net [68.1.0.123]
8 59 ms 23 ms 19 ms mtc3bbrc02-pos0102.rd.ok.cox.net [68.1.0.110]
9 52 ms 51 ms 52 ms lkhnbbrc01-pos0200.rd.at.cox.net [68.1.0.113]
10 50 ms 51 ms 51 ms lkhnbbrc02-pos0100.rd.at.cox.net [68.1.0.3]
11 63 ms 63 ms 63 ms ashbbbrj01-pos030000.r2.as.cox.net [68.1.0.21]
12 244 ms 62 ms 63 ms equinixexchange.peer1.net [206.223.115.30]
13 65 ms 63 ms 64 ms 216.187.115.250
14 65 ms 63 ms 63 ms 69.44.56.67
15 65 ms 69 ms 66 ms www.garykeith.com [69.44.159.54]

Trace complete.
The difference I'm seeing is that you go appear to go through Level 3, which I believe they were having problems with. I can't be positive though as I tend not to pay attention to the network issue threads, since I'm not on SB's network.

Your best bet would be to either PM QT or knightfoo as they're likely to help you get things squared.

[GaryK]

I sent a PM to QT. Hopefully she'll be able to help.

I'm far from being a DNS expert but since both IP Addresses take the same basic route via Level 3 why would my main IP Address work fine while the new one doesn't?

[DXD]

If SB's router is not configured to route traffic for that ip address onto the network where the servers are it would never get through and that's my guess as to what is going on.

[GaryK]

Maybe I am misunderstanding you. But it seems the SB routers are configured correctly as everyone except me can see the website in question.

[DXD]

OOPS I must of missed something then I thought no one could see it cause it was stoping at the router.

If it's just you that can not get to that new ip address then do you have a firewall or something that could be blocking it?

[GaryK]

I assumed no one could see it at first until I found out everyone could see it except me. :)

I do have a firewall and router but they appear to be configured correctly.

My connection makes it all the way to the router that's supposed to hand the connection off to my server and then it just times out. For everyone else though it seems to work fine. That, to me, is what's so puzzling.

[DXD]

How do you have a router on your SB Server? Is this some sort of software router or something?

What firewall software are you using?

[GaryK]

Oh, I thought you meant here at work.

On the server I am using Kerio Server Firewall. It appears to be configured properly as others can access the site, just not me. But that's not even an issue because the connection attempt never makes it that far. It's dropped before it reaches my server otherwise I'd see the failed attempt in the firewall log.

[GaryK]

It's been 24 hours since I reported a problem with my new IP Address and my ticket still has not been assigned to anyone. I'm a very frustrated customer right now and I don't know what to do next.

What does one do when they're basically ignored by SB?

[GaryK]

There was a problem with a SB router and it has been fixed. I can now access my new IP Address.

[KyleMulligan]

I figured that was it. Good thing you got it resolved. :)

[GaryK]

Which reminds me I forgot my manners.

Thank you Kyle and also DXD for trying to help me resolve this problem.

[DXD]

Yea that was my first guess to was the SB router glad they got it fixed for you.