Question
-
Topic
-
Web Browsing issues on Server 2003
LockedOkay this might get lengthy but I want to detail everything I’ve done.
We have a secondary site that we have just opened. We have a DSL connection to the internet with a site-to-site vpn connection for communication between the 2 sites. The server in our B site is running DHCP, DNS, and WINS (old service running in A site, will disable after everything is stabilized). All PCs at B use the DNS server at B and can surf the net, but the server itself cannot. I have tried having the server use the A-Site DNS and even the ISP DNS servers. No matter what, nslookup works, ping works (with sites that allow it), but web browsing doesn’t. No other devices at A or B have a problem, just the B server. This has impacted Windows update and virus protection updates. I want to dcpromo the server, but don’t dare until this is resolved.
B Server is an HP Proliant server running Server 2003 SP2, IP address 192.168.2.100, A server is HP Proliant running Server 2003 SBS, IP address 192.168.1.23.
ipconfig /all
Windows IP ConfigurationHost Name . . . . . . . . . . . . : myhost
Primary Dns Suffix . . . . . . . : subdomain.domain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : subdomain.domain.com
domain.comEthernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit Server A
dapter
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.100
192.168.1.23
Primary WINS Server . . . . . . . : 192.168.2.100
Secondary WINS Server . . . . . . : 192.168.1.23Here are the things I’ve done to try to resolve this:
1) Tried different DNS servers
2) Reset Winsock (using netsh)
3) Reset TCP/IP stack (using netsh)
4) Reloaded NIC drivers
5) Installed Firefox 3.5 (to verify it wasn’t an IE problem)
6) used ping -f -l to find the packet size that worked, and then set the MTU to match (1454, btw).
7) Turned DNS off and on
8) Turned DNS, DHCP, and WINS Server roles off and back on
9) Tried local administrator account and network account, neither works.So that’s it. I’m looking for a 10th and final way to fix this issue. If anyone has any ideas about where the problem is or what I can do to resolve it, I would love to hear back.
Thanks.