DNS WAN and IIS WebSite

January 22, 2009 at 12:44:58
Specs: Windows XP, P4
We have a network with subnet 192.168.115.x with 2003 SBS and we host our website. We have a second lan with subnet 192.168.119.x in a separate building which is connected via wireless bridge. The 119.x users are members of the domain, they can access resources on the .115 network and they can ping, they work just fine. The .115 users can do the same locally and also get to the .119 users. The only problem is the .119 users can NOT access our own website which sits on the .115 network. It's got to be in DNS somewhere but have no idea why or how? Thanks for any help.

See More: DNS WAN and IIS WebSite

Report •


#1
January 22, 2009 at 13:31:40
Try to traceroute your Web-Server from the 119.x net.
What does it show?
Is there a separate DNS-Server for the 119.x network?

Please send a reply, if you solved the problem !!!


Report •

#2
January 22, 2009 at 13:49:21
how do these two lans connect to the server?

via a router or two nics in the server?


Report •

#3
January 22, 2009 at 14:06:51
Both networks use the same DNS and WINS server which is the SBServer sitting on the .115 network. A tracert to www.ourwebsite.com from the .119 subnet displays the gateway and then times out. nslookup from a machine on the .119 network does work and does resolve however. All other websites do work from the .119 location.

Report •

Related Solutions

#4
January 22, 2009 at 14:08:43
The two LANS connect via wireless connection. A simple wireless bridge. The server physically sits on the .115 network in Building A. There are no servers in building B which is the .119 subnet.

Report •

#5
January 22, 2009 at 17:24:35
Check, whether there is a DNS A record and the appropriate PTR record for your Web-Server configured in your DNS-Server.

When such entries do exist, a ping -a ourwebsite.com should reply.

Please send a reply, if you solved the problem !!!


Report •

#6
January 23, 2009 at 05:22:54
Not knowing "alot" about DNS, could you step through where to look and where to add if necessary? Forward Lookup Zone, Reverse Lookup Zone, or in the appropriate IP Subnet under Reverse Lookup Zone. Thank You.

Report •

#7
January 23, 2009 at 15:30:04
The A record have to be created in the Forward Lookupzone, the PTR record must be created in the Reverse Lookupzone.

Please send a reply, if you solved the problem !!!


Report •


Ask Question