Re: No one answered my question?

Just make sure your Gateway is set to your routers IP (probably 192.168.1.1)
and that you have DNS and secondary DNS IP set up (usually your ISP's DNS,
but any will do).
Regards,
Martin


.

Relevant Pages

  • Re: Baffling DNS Problem
    ... Narrowed it down to a local DNS problem. ... info Resolving name ok for: ... Gateway Diagnostic ... Could be either gateway or DNS issue action Automated repair: Reset network connection action Disabling the network adapter ...
    (microsoft.public.windowsxp.network_web)
  • Re: newbie lost in trying to setup NAT
    ... Also make sure you have not configured a default gateway on the private ... that sounds correct for the DNS forwarding. ... > be able to resolve both local and Internet names from this server. ...
    (microsoft.public.windows.server.networking)
  • Re: Cant Connect to Domain after adding Gateway to Internet Route
    ... It was added to the default gateway in our LAN connection. ... >> the router to our alternate DNS settings. ... > static addresses on workstations in the year 2005. ... Those routers are what we also need in our gateway ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem(s) resolving names with natd/ipfw.
    ... Then set all the clients' primary DNS to ... that of the internal IP of your gateway. ... > The problem is that the Windows XP client CANNOT ... > access the Internet with alphabetic names (should be ...
    (freebsd-questions)
  • Re: Domain controller not found
    ... The WAN port on the gateway has an IP of 192.168.0.4. ... All internet traffic ... So the 192.168.0.1 is not longer used on any server or workstation? ... It just seems that the DNS ...
    (microsoft.public.windows.server.setup)