• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2606
  • Last Modified:

Some computers can ping web IP address but cannot resolve ip to domain name

We have  a small business network consists of 15 computers. 2 people bring their own laptop in to connect to our network.

I have tried both a linksys and d-link router. Some computers can connect to the internet using ip address but not by domain name. (Cannot resolve from domain name to IP).

Please advise. Tried changing DNS server to 3 different ones, not doing a thing.

Please advise.

Thanks.
0
nakedconsulting
Asked:
nakedconsulting
1 Solution
 
nakedconsultingAuthor Commented:
An interesting observation, 2 SBS servers can both connect online, 1 Win XP can connect via anonymizer, while all the other Win XP cannot connect except the 2 laptops.

Please advise.

Thanks.
0
 
mojopojoCommented:
Q: You have 2 Windows Small Business Servers on one domain? You should not be able to do that and it may be causing your problem.

http://www.microsoft.com/windowsserver2003/sbs/evaluation/topmyths.mspx

A Windows Small Business 2003 server must be the primary DC on any domain. It must hold the global catalogue. And it must be the primary DNS server. All DNS queries on the domain must point to the SBS Server, even itself (server points to itself for DNS resolution).

You can add secondary DC servers, or file servers, or FTP servers... but they must not be SBS.

0
 
MazaraatCommented:
This sounds like a strictly DNS issue.  I'm assuming your client computers are getting DHCP/DNS from the server?  If not where are they getting it from?

Optimally, one of your SBS servers should be configured to hand out DHCP AND DNS.  In the DNS setup your servers local IP (ex 172.16.1.10) should be listening on, under forwarders put your ISP's DNS server (ex 234.134.5.100).  In DHCP set the scope option (006) DNS Server to your SBS IP that is listening (ex 172.16.1.10).

Any questions?
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
nakedconsultingAuthor Commented:
It has been working like that for a year. Nothing is going to change that now...
0
 
nakedconsultingAuthor Commented:
Everybody is getting DHCP/DNS from the router.
0
 
MazaraatCommented:
If they can't browse by domain name, their not getting DNS.  Make sure your router has the correct DNS IP.  To test, go to a client, go to TCPIP properties, change the primary DNS server to the ISP's DNS server, save.  (may require restart) see if you can browse by name....if not, it may be a bad IP?
0
 
nakedconsultingAuthor Commented:
I called Verizon and get new DNS servers. I can ping them, they work.
0
 
nakedconsultingAuthor Commented:
I use them on the computers too, still not working, please advise.
0
 
MazaraatCommented:
Check to see if your router has a built in firewall, it may be blocking.  What model of router ar eyou currently using, that way I can lookup the settings.
0
 
kmenshouseCommented:
When you said "it's been working like that for a year", then what has changed now?  Were all the clients able to pull proper DNS before now?  Also, can you tell us what OS the XPs are running - pro or home?  What are the laptops running - pro or home?
0
 
nakedconsultingAuthor Commented:
All computers are running pro. One laptop running pro, the other one media center.

Nothing has changed... The problem started with one computer, then another, then another until all but a few of them are working. Yes, everybody was able to pull DNS until now.

DI-634M is the router I'm using.

Thanks.
0
 
robscraigCommented:
If you set the PC's to static IP's and then do a ipconfig /all what are you getting?

That should at least tell you where your PC's are optaining there DNS and DHCP From.
it sounds to me your SBS servers are improperly forwarding DNS queries.

0
 
nakedconsultingAuthor Commented:
They're all on static ip. SBS server doesn't handle DNS or any other internet queres because all traffic points directly to the router.

Thanks.
0
 
screen-nameCommented:
Have you looked into a firmware update for your router? Or reset it, being that you have all your services running on a low end router.

IMHO, you really should run the DNS & DHCP off the server.  Put Verizon's DNS in as fowarders.  But thats just me.

0
 
WickkedCommented:
IMHO, I think this is due to the firewall filtering the icmp traffic on some of the machines.. I might be wrong tho. Just my 2 cents.
0
 
Rob HutchinsonDesktop SupportCommented:
Well like someone else already said, it's a DNS issue so findout why the DNS servers assigned to the workstations that are having problems are no longer resolving names.

Compare the DNS entries for the good PC's with the bad ones, and find out which DNS entries are no longer working an make sure that none of the clients are using these DNS servers.

I'd do a spreadsheet of all the clients on the network and what IP config's they are all using since you have decided to implement static IP's which is alot more work.
0
 
Rob HutchinsonDesktop SupportCommented:
my bad, thought you said you were using static, plz disreguard that part of my comments.
0
 
labtrollCommented:
You say you have linksys AND dlink routers right?

Given you have 15 + users,  I have to assume you are using one as switch
DI-634M is a wifi router.  which one is connected to WAN?
how are they connected together?  [don't connect the second one from  the wan/internet port to the first main one's lan ports...  lan to lan (linksys routers automatically becomes a switch)]

If you using one as a "switch" then you need to set dhcp off on that one (second one).  set it's ip to the range of the main router.

I'm guess you your doing it this way.  Just file sharing server.  SBS is not used as domain controller, (clients don't log into domain but just simple share) so there's no need to point to the server for DNS.

On client, I always set DNS to the main router IP.

correct me if I'm wrong =)
0
 
labtrollCommented:
unless something modified the host files on the computers. virus?

oh, nevermind the stuff about linking the router... you wrote "you TRIED both" routers.  Late nights makes bad eyes  =/

As mentioned before.  Reset router and try also update (if any) of firmware.

Also, turn off wireless and just use wire and try. I had similar issue caused by wireless interference and messing up router.

just throwing in some more possibilities.
0
 
cooleditCommented:
hi, there

what you can try to test TCP/IP stack + DNS.

on a command prompt of a machine working proper.

cmd
nslookup "hit the enter"
what is listed as the DNS server entry
now type google.com enter do you get some respond should say:
64.233.187.99, 72.14.207.99, 64.233.167.99

ok now faulty laptop/desktop
do the same
cmd
nslookup is this the same listed as being the dns server as the one working. if not try this

Type: server "insert the same name as on the one working, or use this one ns1.google.com"
if you use the ns1.google.com it will now be displayed as:
Default Server:  ns1.google.com
Address:  216.239.32.10

now try : microsoft.com and see if this is getting resolved.

Hope that will help you to identify the problem.

Cooledit
0
 
nalanbarCommented:
I hate to be simplistic, but have you done a ipconfig /flushdns on the bad machines? And also, have you looked in the hosts file?
0
 
darimmCommented:
You mentioned that you've tried multiple routers, have you ensured that port 53 (outgoing) UDP/TCP (both) are open on your firewall? Is it possible that a recent Microsoft service pack re-enabled the Windows Firewall on your PCs which was previously disabled? This has often come up as a problem in some enviornments I've worked in. The default configuration for the Windows Firewall is pretty bad. If it is enabled on the machines having problems, try disabling it for troubleshooting purposes.

If it was a single machine, I'd say run 'netsh int ip reset c:\resetlog.txt' to "reinstall" TCP/IP, but since it seems like it's more of a group problem, I'm inclined to think it has something to do with ports/firewall settings.
0
 
nakedconsultingAuthor Commented:
I found out what it was... It was "Spyware Doctor", the new 5.0 version that's causing the problem on each of the computer.

Thanks.
0
 
AnnieModCommented:
PAQed with points refunded (500)

AnnieMod
Cleanup Admin
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now