Solved Have server which won't access internet

June 16, 2011 at 20:16:59
Specs: Windows Server 2008
I have dell office server running windows server 2008, this is at my office, all computers that are connected to server can access the server and access the internet, the server itself however CANNOT access the server. This started all of a sudden

See More: Have server which wont access internet

Report •


✔ Best Answer
June 21, 2011 at 09:29:42
Disable Ethernet adapter Local Area Connection 2:
It should not be enabled.

Go to lan connections and right mouse click on connection2 and choose disable.

The next issue is on Ethernet adapter Local Area Connection:
remove the dns entries listed and replace with 192.168.1.4

We always point the dns server to itself as should all the workstations should point to 192.168.1.4

Do the workstations point to 192.168.1.4 now?

Concerning rdp, you have to go into the router and forward port 3389 to 192.168.1.4
Then from home to access you type in the wanipaddress:3389 in the rdp session to connect.
If your wan interface is set to dhcp simply go to ipchicken.com to get your public ip address before going home. wan ip=public ip address

The dns setting does assume this server is running dns server, has the forwarders configured and Active Directory.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's



#1
June 16, 2011 at 20:26:28
Sorry, I meant the Server itself CANNOT access the INTERNET

Report •

#2
June 17, 2011 at 13:45:43
go to a cmd prompt on the server
type ipconfig and hit enter
is there a gateway entry?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#3
June 20, 2011 at 07:48:13
Before seeing your recommendation to check on a gateway entry, I ran the diagnose and repair and it repaired the internet connection (I thought). My server did it's normal web based backup that night, but I come in this morning and it is back to where it was, can't get on the internet from server, I ran diagnose and repair again and it is back to being able to get back on the internet, probably will stop working later today though, I assume. I did run ipconfig and right now YES I do have a gateway entry. Incidentally, the original IP Address that I used to log on remotely (from my office/hotel) is no where to be found, could this have changed?

Report •

Related Solutions

#4
June 20, 2011 at 08:04:36
lets see that ipconfig /all for review

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
June 20, 2011 at 09:40:56
I'm not a computer tech, just office owner.. how do I copy the command prompt results and post them here?

Report •

#6
June 20, 2011 at 11:02:49
when in the command prompt and after typing ipconfig /all do a right mouse click on the windowed top bar. You will see edit as a choice. go to edit and then choose select all. This will highlight everything. Then right mouse click again, go edit and then choose copy. Paste into a post here.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#7
June 20, 2011 at 11:09:02
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::504:cc0e:b232:a6fe%12
Autoconfiguration IPv4 Address. . : 169.254.166.254
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3060:310f:adf:2288%11
IPv4 Address. . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:102e:1c74:3f57:fefb
Link-local IPv6 Address . . . . . : fe80::102e:1c74:3f57:fefb%10
Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Administrator>


Report •

#8
June 20, 2011 at 14:03:49
perfect except the command looks like this

C:\Users\Administrator>ipconfig /all
and not like this

C:\Users\Administrator>ipconfig

I get more required info with the ipconfig /all

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#9
June 21, 2011 at 07:44:18
sorry about the delay, I was away from my office for your last post. first off, this morning I checked my server and everything seems to be just fine, STILL HAS access to the internet just as it did yesterday morning...if you remember, yesterday morning I ran the diagnose and repair, it has held up..however, when I went home yesterday afternoon/evening I was unable to access the server using remote desktop connection... as you look at this latest copy and paste, could you please tell me what address I am to use in remote desktop connection...thank you. Right now I am in my office at one of our desktops and I am using this address to type in remote desktop connection: 192.168.1.4 and it is working-let's me access the server, this address DOES NOT work from my home laptop.

Here you go:

C:\Users\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : cmserver
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client) #2
Physical Address. . . . . . . . . : 00-26-B9-52-5B-70
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::504:cc0e:b232:a6fe%12(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.166.254(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 285222585
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-CB-12-47-00-26-B9-52-5B-6F

DNS Servers . . . . . . . . . . . : 66.0.175.146
66.0.144.30
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5716C NetXtreme II GigE (NDIS
VBD Client)
Physical Address. . . . . . . . . : 00-26-B9-52-5B-6F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3060:310f:adf:2288%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 251668153
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-CB-12-47-00-26-B9-52-5B-6F

DNS Servers . . . . . . . . . . . : 66.0.175.146
66.0.144.30
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{A4CB73B5-3659-4E94-9B4C-2F418D6AB
EFF}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:102e:1c74:3f57:fefb(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::102e:1c74:3f57:fefb%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator>

THANKS FOR ALL OF YOUR HELP


Report •

#10
June 21, 2011 at 09:29:42
✔ Best Answer
Disable Ethernet adapter Local Area Connection 2:
It should not be enabled.

Go to lan connections and right mouse click on connection2 and choose disable.

The next issue is on Ethernet adapter Local Area Connection:
remove the dns entries listed and replace with 192.168.1.4

We always point the dns server to itself as should all the workstations should point to 192.168.1.4

Do the workstations point to 192.168.1.4 now?

Concerning rdp, you have to go into the router and forward port 3389 to 192.168.1.4
Then from home to access you type in the wanipaddress:3389 in the rdp session to connect.
If your wan interface is set to dhcp simply go to ipchicken.com to get your public ip address before going home. wan ip=public ip address

The dns setting does assume this server is running dns server, has the forwarders configured and Active Directory.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#11
June 22, 2011 at 14:26:51
Thanks a bunch, this is a little deep for me, I did disable connection 2, however, the rest of this scares me, are you able to walk me thru this step by step, I don't want to mess up my office network?? Do you have any idea why I CAN access the server (as in I can get on the server from the desktops in my office which are wired direct to the switch, to the server/modem, I do this by using remote desktop connection and typing in 192.168.1.4 as the IP Address) but this same scenario DOES NOT work from my home????. Thank again for the help. Incidentally, my server is still working fine as far as being able to access the internet... just can't log in from home. Also, I occassionally get message that says IP Conflict, another computer is using the same IP Address?????

Report •

#12
June 23, 2011 at 21:01:17
Your router has to be configured for port forwarding for you to acces via the internet.

You don't want just anyone getting to your server which is why this exists
.
You have to port forward the rdp port 3389 to the static ip of your server.

I could tell you how to do this but it would be painful for both of us :-)

I am also blind to your network so there maybe other issues my helping may exacerbate.

See if you can't find someone in your area you can have come in and setup the port forwarding and make the changes I have recommended on the server.

That ip conflict message is most likely causing your internet outage issue. That needs to be located and resolved.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Ask Question