cannot connect to companyweb internally from client
I have just installed an sbs 2003 server where previously there was just a workgroup. I have one client pc setup that can do everything I ask it. Companyweb works, exchange/outlook works, etc.
I added another existing client pc to the sbs domain. It connects fine, I can get to shared folders on the server, I can get out to the Internet no probs. It is using DHCP & DNS provided from the server.
i can use remote desktop to login to the server from this client pc too. The server responds to a ping on the name and the ip address.
All the client pcs are running MS Office Pro 2007.
I tried to setup Outlook on the client to talk to the Exchange server and it can't "Check Name". It says Outlook is offline. I pursued this problem to no avail for a while and then realised that I couldn't connect to http://companyweb from this pc either.
http://companyweb/ gives me "IE cannot display this page"
http://local.servername/exchange & http://local.servername/remote both return an authorisation warning that "the reuested URL was not found on this server"
this is a real problem because this PC belongs to the org's CEO!!! and it was working till I tried to connect it!
Any clues????
I added another existing client pc to the sbs domain. It connects fine, I can get to shared folders on the server, I can get out to the Internet no probs. It is using DHCP & DNS provided from the server.
i can use remote desktop to login to the server from this client pc too. The server responds to a ping on the name and the ip address.
All the client pcs are running MS Office Pro 2007.
I tried to setup Outlook on the client to talk to the Exchange server and it can't "Check Name". It says Outlook is offline. I pursued this problem to no avail for a while and then realised that I couldn't connect to http://companyweb from this pc either.
http://companyweb/ gives me "IE cannot display this page"
http://local.servername/exchange & http://local.servername/remote both return an authorisation warning that "the reuested URL was not found on this server"
this is a real problem because this PC belongs to the org's CEO!!! and it was working till I tried to connect it!
Any clues????
aubertmr
If you're going through a proxy, make sure that the "bypass proxy server for local connections" is checked in the connections tab in the internet options. If it is or you aren't using a proxy, try getting to the site by IP address. If you can get to it by IP, check your CEO's DNS settings and make sure he's pointed to the right DNS server and make sure the records in DNS are correct.
BTW, if you're having multiple problems resolving from DNS, it's probably something wrong with the DNS settings on that computer. Make sure the DNS suffix is correct. Do an NSLOOKUP and try to find your domain. When I'm having DNS problems and everything looks alright, I've removed the computer from the domain and re-added it.
Well, since you said, your Outlook is Offline ,
Do you have a Personal Firewall or applications like Symantec 360 ? . .. Uninstall it , restart the PC and try ...
Uninstall any antispam / antivirus software, disable Firewalls .. .
Manu
Do you have a Personal Firewall or applications like Symantec 360 ? . .. Uninstall it , restart the PC and try ...
Uninstall any antispam / antivirus software, disable Firewalls .. .
Manu
ASKER
There is no proxy.
If I use the internal ip address with /exchange or /remote I can get in. If I use the external ip I can't find the page. If I use http://local.servername.exchange or remote I the warning that the requested url was not found on the server.
DNS is provided from the server via DHCP. The DNS servers showing on the computer are the DNS servers from our ISP that the computer gets from the server.
i have already removed the computer from the domain and reconnected.
"Make sure the DNS suffix is correct. Do an NSLOOKUP and try to find your domain." how do I do this?
If I use the internal ip address with /exchange or /remote I can get in. If I use the external ip I can't find the page. If I use http://local.servername.exchange or remote I the warning that the requested url was not found on the server.
DNS is provided from the server via DHCP. The DNS servers showing on the computer are the DNS servers from our ISP that the computer gets from the server.
i have already removed the computer from the domain and reconnected.
"Make sure the DNS suffix is correct. Do an NSLOOKUP and try to find your domain." how do I do this?
ASKER
Manu,
I have a Sophos AV & firewall installed exactly the same as on the first client pc. I started with Symantec AV when I first had the prob, so then I got rid of that and put on sophos because I konw it works. i have checked the sophos logs and there are no relavent blocks shown.
Greg
I have a Sophos AV & firewall installed exactly the same as on the first client pc. I started with Symantec AV when I first had the prob, so then I got rid of that and put on sophos because I konw it works. i have checked the sophos logs and there are no relavent blocks shown.
Greg
Your server will be running DNS, it has to to run Active Directory. That's where you want your computer's DNS to point to. The DNS on your server will have the records for itself, because they should update automatically. That would also be why you can't get to your exchange server. Your ISP has no idea what services are on your network.
ASKER
Aubertmr,
So are you telling me that I need to add the servers IP to its own DNS configuration????
So are you telling me that I need to add the servers IP to its own DNS configuration????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just went to manually set the DNS on this computer to the internal IP of the server and discovered that I had previously (when it was still on the w/grp) set the DNS to that of the ISP. So it wasn't getting DNS from the local server at all! Doh!!!
Thanks heaps for ur quick response and pointing me in the right direction. it all makes sense now and I know what NOT to do in the future!
regards,
Greg
Thanks heaps for ur quick response and pointing me in the right direction. it all makes sense now and I know what NOT to do in the future!
regards,
Greg
DNS is a tricky thing. I've messed it up plenty of time and spent hours pulling hair trying to figure out what went wrong.