jmair

LOL, seriously I was looking at the DNS server for hours.. Pulling my hair. You said DHCP and I knew right where to look.. This should resolve it.. Thanks a ton!

When I go to a client machine and ipconfig /all , it has three DNS servers. We only have one. How do I remove the two unwanted?

well, i think i found the problem... I went back to that client machine and although it does have our DNS server as the primary DNS, there is also a second and third!.... Now i need to figure out how to get rid of those. Thanks again.

Thanks for the quick reply. Unfortunatly I've checked several times and the ipconfig /all looks fine. We only have one dns and it's been the same for all machine's i've checked. (It looks very much like mine, however mine is a static ip and hasn't had the problem.) What throws me off completely is that of the four machines on site, it will only not be able to resolve to one of those servers by name. It could be the exchange, or the fileserver or the webserver. It's random. also if I do an nslookup, the return is our single dns server. looks fine there also.

I just had a machine do the same issue (unable to connect or ping a server by name but it can by ip. And it's only to one random server, not all of them.) I did an ipconfig /all it gets a dns and ip. I checked the DNS server and saw only one IP of 10.1.1.100 given to this machine and no other. This seams to be totally random, any thoughts on even where to look for an answer?

We have one DC and it also holds the Global Catalog.

Confirmed that the client machine gets the DNS address.

Only one DNS server giving out 10.1.1.2. What's odd though is a machine that is effected won't have access to any number of servers. For example, it wont be able to get to exchange server by name or the DNS/DHCP server or the file server at random. The next time it happens to a client machine I'll check if it grabbed a DNS ip from the dns server (I'm fairly sure it does though.)

Thanks for the quick reply. I'm not sure what your asking exactly. So I'll answer the best i can. The DNS and DHCP are on the same server. The scope is 10.1.1.x to 10.1.2.x. I've checked the ip's on the client machines and they are within that scope.

I hate to shamelessly bump this, and I don't have much additional info to add however I would gladly give it to help troubleshoot this issue. The additional info is: This issue isn't restricted to just the exchange server, it's also to our fileserver where users drives are mapped. Of course they can't connect to the Server, their mapped drive fails to connect. Also unable to ping the server by name, but I can by IP.

I'm having an issue where some users (randomlly) dont have access to our mail server internally. They are dynamic ips. I have noticed that none of the static IP machines are having this issue. also, if I go to the client machine directly, I'm able to run ipconfig /registerdns and it will resolve the problem (the client can ping all servers by name) for a random amount of time (an hour to a few days). Any ideas what would be causing this?

First I clear out my DNS forward lookup, then after a week I have my list of computer names. YOU can then slect all or right click and export that list of computer names to excel. I'm not sure exactly how accurate that is, but that's what we do.

Thanks! I'll give this a shot. I didnt know that admin commands could be run on startup.

We're currently having some kind of DNS issue on our network and a local workaround is to ipconfig /registerdns I would like to (untill the issue is resolved) add this to the login script, but i requires admin rights. Is there a way that I can do this in the login script with a runas? Unless somebody knows another way around this. Thanks

I struggled with this issue and then found the greatest piece of software. JDiagnostic It's a diagnostic and easy setup wizard for joomla 1.5 and your AD.

This issue is still a thorn in our side, but I have some more info. The webserver itself can not connect to the internet. (i.e., I can't access google from it.) So I'm wondering if it has anything to do with the nic card configs. Here are screen shots of both nics. I'm also unable to connect to OWA from the webserver itself, but I can from my work computer connecting to 10.1.1.5 (internal website). Internal 1 2 3 External 1 2 3

Details details, here we go. I have a Web Server with two nics. 10.1.1.x for interal access, and 10.2.2.5 with a direct DMZ to the www. The website works fine on both nics. OWA works fine on the 10.1.1.x nic (or connecting from the inside.) The firewall has one access rule for the DMZ, that's ALL traffic to DMZ both ways. The server has two webservers(services) running. WAMP and IIS. WAMP for the website and IIS6 for OWA. Things I've tried. (the not so obvious) 1: I've created a new website in IIS using the same SLL cert directing to a folder named exchange with a file named text.txt inside. When connecting to it from outside, it prompted for user/pass, then directed me to the text.txt file. Works fine. Confirms that the firewall is wide open and ssl ports work fine. 2: I disabled the 10.1.1.x nic on the webserver to force this test, to make sure there is no issue with 10.2.2.x and 10.1.1.x for some reason. Other Thoughts 1: Could there be some DNS HOST, A, MAIL or something added for this? But it works internally, just not external. And our normal mail works just fine. Just a thought, but not sure where to look. I've been wrestling with this for a few days, any thoughts?

Thanks for the info!

We have our backbones using fiber, then to cat5. Cat5 for single machines in the labs, and cat5 on our Gigabit switches going to our servers and to the firewall > t1 router. A few years ago, there was cat6 and cat5e (something never put in place here). Am I missing out? Am I losing anything by using cat5 for some the high traffic switch ports (like the fileserver and internet)?

1:Are you going through an external smtp server on your isp or is your smtp server trying to talk to mail servers directly. The flow would look like this. www > t1 > firewall > sonicwall > Isa > Exchange Server and Users. 2:Does a telnet to a mx record on port 25 work? I tried the following line from telnet, I think this should connect me? (followed instructions from How to Use Telnet to Test SMTP Communication) Type open mail1.fabrikam.com 25 and then press ENTER. Connection Failed. I also tried mine. mail.parkcountyre2.org 25 ... Also failed. 3:I am assuming exchange has gateway ip etc all set. I'm assuming it is also =) . IP flow works fine and haven't seen any issues yet. 4: What does your current ruleset for isa have? Allow DNS to my DNS server. Allow SMTP traffic to Exchange server. Allow outobund SMTP traffic from Exchange server.

*update* I've tried nslookup on myself and it works fine. But doing an nslookup on an external location fails. I've added a DNS rule for ISA, from extrenal network to the DNS server.

I have an ISA 2006 as our proxy. I've published our Exchange 2003 server and we are able to receive all outbound email. We can also send/receive all internal email. But we can't send email to the internet. To check if DNS is working on my end I've done the following. Checked the DNS forwarding on my dns server and it also has my ISP DNS ip there. We can access the internet from any location (checking dns again) Also able to ping all servers by machine name, not just by ip. Flushed the Arp on a server and pinged by name again, just to be sure. I've contacted our ISP, he says everything looks good on their end. Baffled and a receiving a few calls about the email bounce backs. Any suggestions would be welcome.

I currently run Wamp and IIS on the same Win2003 server. Although I only need IIS for OWA, it has worked flawlessly (for the most part) and I love Wamp. *note, i'm aware this post has not true value to the OP, just to help assure that it's not a bad path to take.

Thanks for the reply. I am still trying to resolve this issue though. 1:Have you enabled remote desktop on the machines. Yep yep. 2:Is a terminal server an option? My kneejerk reaction is "No", but it's only because I have no idea what it is. 3:Have you looked at the secure gateway features in server 2008? There is no Server 2008 on site, no funds for it anytime soon.

I'm able to configure ISA to allow RDC from machines on site, however I'm having troubles setting it up so I can connect from off site. I've created a NAT on a free outside ip address that routes directly to the internal ISA server. (This is only a temporary thing) The outside RDC is unable to connect, so I redirected destination ip of the NAT to go to a non ISA server and it connects just fine (so I know it's not a firewall or nat issue.) I don’t want to go into detail of what I've done, hoping not to persuade suggestions on what else to do. I'm not void of overlooking the obvious. Any suggestions are welcome. Jesse