Mozilla Failing on Server Holding Active Directory

February 12, 2015 at 04:30:47
Specs: Window Server 2012 R2, Intel Core i3-3240 CPU @3.40 GHz / RAM 16GB
Good afternoon I have a server where I have installed AD, ADCH and DNS for a small Lab. All machines connected to the domain on this server are able to browse an ADSL internet service.

The ADSL is connected to an DLink switch and the server is connected to the switch. I have used IPConfig/flushdns, reset, release..etc.

The Open Network and Sgaring Tab is showing that this server connected through Ethernet is showing activity for both Sent and Received. However Mozilla is showing that Connection has been reset.

The machine has a static IP (auto IP is also failing)


See More: Mozilla Failing on Server Holding Active Directory

Report •

#1
February 12, 2015 at 04:45:54
Have you tried web browsers other than Mozilla, or tested any other Internet services? How about tests via ping or traceroute?

I'm a bit confused by your remark that the machine has a static IP because auto IP is failing. How could you set up an Active Directory and DNS server without using a fixed address? You don't mention DHCP. Is the server providing DHCP? If not then I think your first step is to set that up and disable any other DHCP server on your network.

Edit: Silly question no doubt but the fixed IP address that you have used is on the same network as your router and the other computers?

message edited by ijack


Report •

#2
February 12, 2015 at 05:43:54
Both AD, DNS and DHCP are on the same machine. I was able to setup the Active Directory using static IP address and Domain is up and running with 5 computers connected to the domain. When I tried to run updates I noticed that Mozilla and IE both cannot connect to the internet. Whilst I can see that the server is receiving and sending data packets on the Ethernet Status (Sent 65,000 bytes and Received 32,000 bytes).

I had tried removing the static IP and tested auto IP - this too is not allowing me to connect to internet. Mozilla has error : "The connection was reset. The connection to the server was reset while the page was loading :
1. the site was temp unavailable or too busy
2. If unable to load any pages check computers network
3. If protected by firewall or proxy make sure that firefox is permitted to access the web"

message edited by Mpala


Report •

#3
February 12, 2015 at 05:57:40
I have tried using a tracert to/on www.google.com. I am getting :

C:\>tracert www.google.com

Tracing route to www.google.com [197.220.0.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 301 ms 190 ms 94 ms 172.21.0.1
3 180 ms 207 ms 211 ms 172.16.10.252
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 450 ms 374 ms 423 ms cache.google.com [197.220.0.22]

Trace complete.


Report •

Related Solutions

#4
February 12, 2015 at 06:07:02
Further Details I have run :


cmd /c "ipconfig /all > postme.txt & ping yahoo.com >> postme.txt & notepad postme.txt & del postme.txt"

Results :

Windows IP Configuration

Host Name . . . . . . . . . . . . : Nick
Primary Dns Suffix . . . . . . . : corp.XXXXXXXXX
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : corp.XXXXXXXX

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : BC-5F-F4-93-7A-DC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.10
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled


Pinging google.com [197.220.0.24] with 32 bytes of data:
Reply from 197.220.0.24: bytes=32 time=558ms TTL=55
Reply from 197.220.0.24: bytes=32 time=443ms TTL=55
Reply from 197.220.0.24: bytes=32 time=417ms TTL=55
Reply from 197.220.0.24: bytes=32 time=367ms TTL=55

Ping statistics for 197.220.0.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 367ms, Maximum = 558ms, Average = 446ms


Report •

#5
February 12, 2015 at 06:47:42
Could be a firewall problem. Try turning the firewall off and see if the problem persists. I would only do that for testing purposes; if it solves the problem then you need to turn it on again and cofigure rules to allow outbound traffic on http and https ports.

Report •

#6
February 13, 2015 at 03:26:27
Firewall is turned off no access yet

Report •

Ask Question