1)what is ping? 2)difference between DNS and DSN?
102590
Ping can be used to see if another server is running or to measure the distance to another servers. It is short for Packet Internet Groper. A utility that forwards data packets to check the quality of a link or verify the connection of a machine to the Internet.\n\nThe domain name system (DNS) is the way that Internet domain names are located and translated into IP (Internet Protocol) addresses. A domain name is a meaningful and easy-to-remember "handle" for an Internet address. Because maintaining a central list of domain name/IP address correspondences would be impractical, the lists of domain names and IP addresses are distributed throughout the Internet in a hierarchy of authority.\n\nwhile\n\nA DSN stores the data source information necessary for the Driver Manager to connect to the database. This can be configured either through the ODBC Administrator or in a DSN file. On Windows, the information is called a system or user DSN and is stored in the Registry. Data source information can also be stored in text configuration files, as is the case on UNIX.
1094664
Actually DB server hostname/DSN has been provided by you web hosting company this details you can get from there.\nYour Database Name: in that server hosting tem has alcotated some db to you website\nDatabase Username/ Password: to authaticate you\nprefix for table in database for more information go to Source
1083450
First use ipconfig from command prompt ipconfig/all shows your DNS servers ip addresses. Next use ping to ping them, if ping gets a reply you can try to use nslookup that connects DNS server, you know the application that shows the error could have it's own problems.\nIf it is a real dns problem and you are using dhcp, you could try to ipconfig/release and ipconfig/renew.\nIf that doesn't work call the customer support, because having an Internet connection without DNS is quite useless and you should get your money back.
142452
1. The difference between NAT, public, and private addresses. First public addresses. These are addresses by which others on the internet can refer to you. Another way to think of it is these are the addresses that are visible to people outside your LAN. Private addresses are just the opposite. These are the addresses that are used on your local network and they are not used outside the LAN. Thus if you encounter internet traffic from an address like 10.1.1.5, you can safely disregard it. NAT, or Network Address Translation, is done at your firewall or gateway and it essentially translates your private address into a public address. For example, your local network may be using addresses in the 192.168.1.0-254 range. These are private addresses and cannot be used on the internet. When you try to access the internet, your firewall or gateway translates that address to your public address. Thus, if you have a very simple network with only one public IP address, you could have, say, 10 clients on your internal network, but when they access the internet, they all appear to come from your single public address. Then there is static NAT (SNAT) and dynamic NAT (DNAT), but that's a little outside the scope of your question. \n2. Where to enter the public address. When you say that you have one of the clients acting like a sever, I assume you mean that it is functioning as the firewall/gateway? If that is the case, this is the only box on which you need to have the public IP address. This is for your outside-facing interface, and your private address will be on your inside-facing interface. Your other client machines don't have any need or use for the public IP address.
175353
DHCP: Dynamic Host Configuration Protocol. Suppose a computer belonging to a network and without a fixed IP address. When it is turned on, it requests network configurations (this request is sent as a broadcast request - everyone in the network can listen, but only a DHCP server will answer). The DHCP server answers this request with informations as IP address, netmask, gateway IP, DNS server, and so on. This IP address can be valid by a period of time (depends on the DHCP server configuration), and, when this period is over, another network configuration request is sent to the DHCP server.\n\n\nDNS: Domain name system. It is used to translate IP address in  readable (or sometimes not ;-) ) names. For example: when you type www.yahoo.com in address field of your browser, a request is sent to your DNS server (that can be fixed or got by DHCP request) and the server answer with the IP address of that name. With this address you can do all the communication needed. The inverse also can be done: you request the name of a host and the DNS answer the name of that host. Below is a link for BIND site, which is a very used DNS server. And a HOWTO too ;-)
56995
in windows go to 'run' and type: cmd\n\non the command line write: ping <DNS address>
1070372
1) Short for Domain Name System (or Service or Server), an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they're easier to remember. The Internet however, is really based on IP addresses. Every time you use a domain name, therefore, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.example.com might translate to 198.105.232.4. \nThe DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.
278083
Normally it's about 24 hours to propagate across the US.   \nonce the DNS is Set for the domain, that is 'fired' off to other DNS servers, that branch out to others servers, etc until everyone is update with the new location.
914972
moyah8, ping is to find out whether the host is alive or dead. it's not for sending messages. if you want to send message, type "net send <ip_address> <message>" the <ip_address> can be a specific ip that is in your network or your subnet mask. please note that if you use subnet mask, the message will be sent to all clients that are connected to your network. however, this sending message thing won't work if you're sending message to any other people that is not in your network.
673697
if you try to ping the domain name im assuming that you are unable to resolve the host name.  If this is happening make sure in TCP/IP properties that you have the DNS Server Addresses right (or in your dhcp setup... whatever provides your network info)  If that is set up correctly make sure that DNS is running on your server (that the service is started)  If that is fine I would assume that your DNS is setup Incorrectly.  You might want to try to get a basic setup of dns on it to test it.  Its hard to give steps with out knowing more details (type of server, Network layout, type of workstation, Linux, Unix, Mac, Window, Dhcp, static IP address)
193684
NET SEND {name | * | /DOMAIN[:name] | /USERS} message\n\nexample net send 150.0.150.10 "hi"
319778
ping -a <ip address>\n\nTo query a specific DNS server use NSlookup from command line then do a ls for PTR records.  Or use an online IP whois tool.
64894
Try clicking Start, Run, and type in "cmd" without quotes, then click OK. Then type "ipconfig /flushdns" without quotes and hit ENTER. This flushes your local DNS cache.\n\nDNS is a way for your computer that google.com = 72.14.207.99. It translates internet names into IP addresses. The DNS cache is a local copy of all the DNS requests your computer has made to DNS servers, which saves time so it won't have to request it next time.\n\nBe aware: the answer below (IE history etc) will not clear your DNS cache. It only clears History, cookies and IE settings.
139510
I would check to make sure that you have a good DNS setting on your machine.\n\nIf you're on a home network and the pc is set up for DHCP then the pc gets the DNS info from the router and the router gets it from the ISP.  you can add a second DNS lookup to the network config that will go to a 3rd party DNS server for name resolution.\n\nDo a search on DNS servers and there are a bunch of them listed out there that are public.  Then you just add that to your network settings under the DNS tab.  You will still use the DHCP DNS settings if it can resolve properly, but if you attempt to hit a site that the primary DNS doesnt know about then it will try to use the external DNS.
962076
you need to have a primary and secondary domain name servers - dns .. call your internet service provider they can provide you the dns after that call linksys and ask  where to put these dns. \n- you can also call your internet service provider and complain about this - your internet service provider might ask you to bypass the router (usually isp doesnt support 3rd party hardware) for troubleshooting.. if first tier tech support cant resolve your issue, they have second tier support for further troubleshooting\n- also you can try different browsers
204748
One appears to be a complete IP address and the other is not. For the address to be complete there must be 4 numbers separated by dots (xx.xx.xx.xx).\n\nTypically, your computer uses one address to communicate with other computers within your local network (like your home or office) and shares a single address with computers outside your network (like on the Internet). This is done by your router or cable modem (assuming you're at home) by a process called network address translation (NAT).  On the router config page you often see a LAN and WAN address, with the WAN (wide-area network) address being the one for the internet connection to your service provider and the LAN (local-area network) address being the one used to connect to all of the other computers in your home or office. All of the computers in your local-area network will get addresses that are in the same "subnet" as the router.\n\nThere is no "difference" between one number and another as long as you're using an address which is valid on your network. The most important thing is that your local-area IP address is accompanied by the correct subnet mask. That's the one that usually looks something like 255.255.255.0. If you aren't sure what these mean, you need to talk to the network administrator or help desk for your internet service provider.
609251
What factors need to be checked?  And buying your own server is pretty simple however hosting your own DNS could be more worrisome if you don't know what you're doing.\n\nIt all depends what you plan on putting on your website and how much data is going to be transmitted as most hosting companies (shared) will charge you extra if you run over your bandwidth limit.