Cannot go on the internet

  • Thread starter Thread starter Filip Mato¹iæ
  • Start date Start date
F

Filip Mato¹iæ

I have a win 2000 server machine and i can't get it to go on the internet!
I can ping any web site and tracert it but when i open my explorer and try
to get www.google.com it says (after a while) "Explorer cannot connect to
the search page"
as an alert box. The server has no IPsec policy set. It is in a private
network. My local machine goes to the net fine from the same network. At
first i thought that my firewall is the problem so to avoid reconfiguring
the firewall and to go straight to the net i pluged it into a ISDN router
( so it goes througho an ISP), it opens the ISDN channels fine but still the
same problem. When I plugg in my local machine it goes to the net witout any
problems. I turned off the proxy server in the explorer ->internet
options->connection->lan settings.
Anybody know where is the problem?
THX
 
If you can ping by ip but not by name, it is obviously a DNS issue. Where
are you getting your machine's ip address from, DHCP? If you get a static
address from your ISP, you need to specify the correct DNS server's ip
address in your tcp/ip configuration. You get that from your ISP.

Or, to make it easier, why not just look at the settings on the machine that
works and compare them with the machine that doesn't work. They should be
the same except for the machine's ip address.
 
This is an exchange server so to my local machine it is the DNS server,
i can ping anything by adress or by name from my server. But to avoid all
complications
i gave it the IP adress same as my local computer ( before, i turned off my
computer )
as the server is my DNS server i left that to be the same and it still
dosen't work.
The next thing i done is i plugedd the network cable into a ISDN router
which i setup to call my ISP when the IP adress of the router is called and
when i try it with my local comp it works fine but when i try with the
server it dosent. I allso changed the DNS adress on my server to the one
given by my ISP and still it dosent work?
 
I allso tried the telnet (server IP) 80 and 25 from my local comp
the port 25 response is OK but 80 dosen't. I think there is something
blocking the inbound traffic. I allso have another two servers ane is an
aplication server and the other is a web server and they all have the same
problem. They are behind a firewall but when i unplug them from the
firewall, and plug them into the network as my local computer and set there
gatway to be the ISDN router (so they dont go through the firewall but
through my ISP)
they all dont work. I thought there might be somwhere in the win2000 server
OS a way to block the HTTP port i checked if there were any IPsec set but
no!
 
Your second sentence says you can ping by ip address or by name from the
server, soooo that suggests now that there is no problem with DNS, and you
need to really clarify what is the problem. Is it ONLY via a browser that
you cannot connect to the internet?

As for your network(s), are you saying you have two different network
connections to the internet? One ISDN and the other one is what???????
Please be specific and figure out which network you are trying to
troubleshoot. Also, now you are saying that the server in question is your
DNS server, that is a whole different story.

If your local computer was working before through your regular network
connection, and it goes to your server for DNS, then what changed? Run
ipconfig /all on both machines and post the results here. As for the DNS
issue, can you ping your ISP's DNS server? Please don't give the server the
same ip address as your local computer, it should have it's own ip address
and if it is running DNS services for the rest of your network, it's own DNS
settings need to point to itself with DNS forwarding setup to point to the
outside. This is done through Administrator Tools>> DNS. Please read up on
this subject as it is not something you should be playing around with if you
don't know enough about it.
 
My server
Ip 192.168.0.2
DNS 192.168.0.2
subnet 255.255.0.0.
gateway 192.168.10.100 -> this is my ISDN router

ISDN router
Ip 192.168.0.2
subnet 255.255.0.0
DNS 192.168.10.100
The router calls my ISP for internet service

My local comp
Ip 192.168.10.3
DNS 192.168.0.2
subnet 255.255.0.0
gateway 192.168.10.100 -> this is my ISDN router

the local comp goes to the internet the server dosent
 
Yikes!! Your router and server have the same ip, that's bad. Your server
and local machine are in different ip ranges, that's confusing. Why don't
you have them in the same range? I don't understand the router's DNS entry,
it should not be a private ip address. I'm not that familiar with ISDN
devices, but it seems it should be pointing to your ISP's DNS server. So
call your ISP and ask them what the ip address is for DNS. Also, this
doesn't answer any of my questions from my previous post. It's a little
difficult to help soneone if they can't/won't answer questions. I'm not
going to suggest the correct ip addresses for you because I don't know the
details that you still have not provided about your overall network, like
why, where and the purpose your DNS server fits into this scheme.
 
I'm sorry i miss wrote
this is ipconfig /all for my local
Dhcp Enabled No
IP adress 192.168.10.3
subnetmask 255.255.0.0
Default Gateway 192.168.10.100

this is ipconfig /all for my server
Dhcp Enabled No
IP adress 192.168.10.3
subnetmask 255.255.0.0
Default Gateway 192.168.10.100

this is for my ISDN router
IP adress 192.168.10.100
subnetmask 255.255.0.0
DHCP Disabled
How the ISDN router works is same as an ISDN adapter just that it is on a
network
, when I open the explorer (on a computer, let's say my local comp) my
router opens the ISDN channels (as it is the default gateway) calls my ISP
and connects to the internet.
My DNS server is my "server". I allso tried putting the DNS adress of my ISP
on my "server" and my local pc, the pc can access the net the server can't.
I even changed the IP adress of my server as follows

IP 192.168.10.4
subnetmask 255.255.0.0
Default Gateway 192.168.10.100
DNS 195.29.150.3
alternative DNS 195.29.150.2
Just so that I can see if the problem is the IP adress, but still nothing.

I thought that ther is a problem in some kinde of ipsec, but there were none
set.
Im sorry if I'm writting a bit confusing, English is not my native language.
THX for your patience.
 
I feel like I'm taking a Microsoft cert exam :-(

Filip Mato¹iæ said:
I'm sorry i miss wrote
this is ipconfig /all for my local
Dhcp Enabled No
IP adress 192.168.10.3
subnetmask 255.255.0.0
Default Gateway 192.168.10.100

this is ipconfig /all for my server
Dhcp Enabled No
IP adress 192.168.10.3
subnetmask 255.255.0.0
Default Gateway 192.168.10.100

this is for my ISDN router
IP adress 192.168.10.100
subnetmask 255.255.0.0
DHCP Disabled
How the ISDN router works is same as an ISDN adapter just that it is on a
network
, when I open the explorer (on a computer, let's say my local comp) my
router opens the ISDN channels (as it is the default gateway) calls my ISP
and connects to the internet.
My DNS server is my "server". I allso tried putting the DNS adress of my ISP
on my "server" and my local pc, the pc can access the net the server can't.
I even changed the IP adress of my server as follows

IP 192.168.10.4
subnetmask 255.255.0.0
Default Gateway 192.168.10.100
DNS 195.29.150.3
alternative DNS 195.29.150.2
Just so that I can see if the problem is the IP adress, but still nothing.

I thought that ther is a problem in some kinde of ipsec, but there were none
set.
Im sorry if I'm writting a bit confusing, English is not my native language.
THX for your patience.


with get
Click to expand...
 
Let me try to explain this. If your server is running DNS as a service (DNS
Server is running in the Services applet), then your clients should be
pointing to it for all DNS. This server then should use forwarding to send
DNS lookups out to the Internet. In this case, the server's TCP/IP DNS
entry should ALWAYS point to itself. So if the server's ip address is
192.168.10.4, then it's own DNS entry should also be 192.168.10.4. Also,
your clients will use the same ip address for DNS.

You set up forwarding in the DNS applet in adminstrator tools on the server
as I mentioned before - have you done this? It is a critical step and your
DNS server will not function properly until you do this. This is where you
will use your ISP's DNS (195.29.150.3 and 195.29.130.2).

Hope this helps.
 
The forwarding was the problem thx.
serverguy said:
Let me try to explain this. If your server is running DNS as a service (DNS
Server is running in the Services applet), then your clients should be
pointing to it for all DNS. This server then should use forwarding to send
DNS lookups out to the Internet. In this case, the server's TCP/IP DNS
entry should ALWAYS point to itself. So if the server's ip address is
192.168.10.4, then it's own DNS entry should also be 192.168.10.4. Also,
your clients will use the same ip address for DNS.

You set up forwarding in the DNS applet in adminstrator tools on the server
as I mentioned before - have you done this? It is a critical step and your
DNS server will not function properly until you do this. This is where you
will use your ISP's DNS (195.29.150.3 and 195.29.130.2).

Hope this helps.

question point in
Click to expand...
 
Back
Top