- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
DNS-servers translate names, such as 'www.fixya.com' to IP-addresses, because routing of IP-packets on the Internet is done using the IP-addresses, not by using the names of each computer.
If you have a router between your computers and your cable-modem (or DSL-modem), then the router can automatically supply the "Primary DNS Server" and "Secondary DNS Server" and "IP Address" to your server computer, if you configure the network-adapter on the server to "automatically obtain an IP Address".
As long as you leave your server running, the "dynamic" IP-address that it obtains will, in effect, become a "static" (namely "non-changing") IP-address.
For that connect your router to directly to lan ports of your server.and install another ethernet lan card on server so that ports connect with switch. Then configure your router as bridge connection then set dns as your server ip in all computers.Then you can get 100% fast internet. Let me know if you need further assistance. Thanks for using FixYa.
hello, is your server 2003 setup as DNS server??? if so have you configured forwarder for non- local access? is that a home? or business? is it work do you not have a static public IP address.
here whats happening, when you manually give client the DNS they can resolve everything local fine but when a request for outside world is sent your server doesn't know what to do with it. log on to server open up your dns console, right click on your domain, then select properties, find forwarder tab and add a any reliable public DNS server there ( ie I use 4.2.2.1 (att)) server pretty quick and reliable.
so next time a request is sent to your server and server doesn't have that information it forward that to the public DNS and you will be good to go.
but from your setup i am gathering there is plently you do to improve your network and reduce your headache of manual work.
typical setup: 1- setup DNS with forwarder
2- Setup DHCP on Server instead of router ( trust me its easier than you think)
3- put all setting to for clients in DHCP options
4- reserve IPs for servers/prineters/switches etc.
5- set all clients for DHCP
6-disable DHCP on router.
Use static IP addresses. Do not DHCP from the router. Still
use the same DNS and gateway. Just specify an IP address for each
one, preferably not in the DHCP range used on the router.
If the Windows 2003 server is utilized as the DNS server, then yes it should be set to 192.168.1.5. You need to get into the Linksys router via http://192.168.1.1 and under DNS of DHCP if it is set to .1.1. You should be able to change it to .1.5.
Your DNS should be 192.168.1.1, which is the IP of your router, unless you are running your own registered DNS server on Windows 2003.
If you are having issues with loading websites when you go out to the Internet, you may want to log in to the admin account on your router and manually type in the DNS information that the router is getting from your ISP.
You have SP2? Is that for Exchange Server or the SBS 2003 OS or both? Make sure you have the latest Service Packs installed for both. I think that's SP2. Exchange Server has to be updated to work with the iPhone. Check that the settings in IIS are the same for Security, Authentication where to use SSL (although different certificate for each server) etc. for OMA, OWA, Exchange etc.
I hope you don't mind me asking if you are certified?
×