TCP/IP problem?

Dear All

In Win2K the TCP/IP is set to but it failed to response to Dos Prompt Ping. When pinging the host name, appeared. Why?


How to make client/server software work on the same PC?

Best regards
Fa Cheng CHIN
5 answers Last reply
More about problem
  1. Quote:

    In Win2K the TCP/IP is set to but it failed to response to Dos Prompt Ping. When pinging the host name, appeared. Why?

    What is DNS, WINS, LMHOSTS?

    Is any other computer on the network set at is the network card physically connected to the network? (This can cause the "real" ip address of the system not to be known/available). is also known as the "loopback" ip address. Its valid on any computer in the world running tcp/ip. If was not available, then pinging the hostname will also map to (this is fairly normal).

    DNS = Domain Name Server/Service
    WINS = Windows Internet Naming Service
    LMHOSTS = something to do with WINS i think.

    All of these are very well detailed in the help files that come with win2k.

    Now, as far as "How to make client/server software work on the same PC?" thats a different matter. You will have to contact your software provider for details about that as it can vary wildly from software package to software package.

    Ian McGinley
  2. "In Win2K the TCP/IP is set to but it failed to response to Dos Prompt Ping. When pinging the host name, appeared. Why?" is ALLWAYS the local (host)address for TCP/IP. It is supposed to be the IP of your local machine's TCP/IP stack including the physical layer (ethernet card) per Microsoft.
    Normally if you suspect that TCP/IP may be corrupted, you can ping, and if you get good responses, then your TCP/IP, your bindings, and your ethernet card should be functional. This is all founded on the OSI model (7 layer burrito):
    Application (top)
    Physical (bottom)
    When you "ping", you are originating a request at the Application level which "suppposedly" has to travel all the way down to the Physical layer and back up to Application to return a response (ping statistics).
    What a co-worker discovered thou was that it will return good responses even with the ethernet card removed. We contacted Microsoft's engineering division, and relayed this finding to them, and they said "Hm.... We'll get back to you". We have not heard back from them yet.
    I suspect that TCP/IP uses a "Virtual" socket for, and only simulates a hardware response. The real activity is all in software. Your ethernet card also has a MAC address. This address "should" be hard wired individually for every network card made, and should be unique. It is usually expressed in Hexidecimal like this:
    01 10 5e 1f c3 6a
    At a DOS prompt, type in {netstat ?} and you will get a list of command modifiers for the netstat command. These will give you more detailed information about your network addressing. For instance if you enter {netstat /r} you will see your current Routing table and statistics.
    Or in W95/98 go to the RUN line and enter {winipcfg} and hit enter. A new window will open, and you can select either PPP (dialup connection) or your Ethernet card. This will show all settings including TCP/IP address, MAC address, Default Gateway, Sub-Net Mask, etc..
    Any time you change your settings in your network, you should either Release ALL and Renew ALL in this window, or within a DOS window use {ipconfig /release all} and then {ipconfig /renew all}. This tells your computer to relook at your configuration, and change any settings currently in use by your network. If you make changes to TCP/IP, DHCP, etc... you MUST either shut down and restart, or use those previous commands to enable your settings changes to be modified in the network tables.

    When you configure your TCP/IP properties, you can choose to either use DHCP from a remote host for TCP/IP addressing (your ISP usually provides this service) or you can purchase a static IP and "hard code" the IP, Sub-Net Mask, and the Default Gateway. You could get fancier in several ways, like configuring your server as global DHCP client, local DHCP server, letting it pass out local IP addresses, and function as a Gateway for the rest of your local network, or using a static IP on the server, and DHCP internally, or ......
    All different configurations have their advantages and disadvantages depending on your situation.
    Hope this helps.....

  3. I am sorry I didn't understand it all. However you are the right expert to ask the next question.

    How to assign the IP address that I want then?

    Ignoring the explanation and just give me the instruction.

    I have copied your reply and plans to go home and read it 10 tims if I need to, with the help files.

    Best regards
    Fa Cheng CHIN
  4. heh, sounds like dlfuller's been studying for the network essentials exam.

    Anyway, we could use a little more info to help with your problem. Is your computer part of a network? How is that network configured? Do you even have a network card installed?

    You can get a lot of info by typing <b>ipconfig /all</b> - copy and past it here.

    To change your IP address right click on Network Neighbourhood and select properties, then right click on local area network and select properties again.
    Now select tcp/ip, and click properties again. You should now be able to change it.
  5. That was exactly what I did to secify TCP/IP.

    system is Duron 650 to 900, A7V, yes there is a network card, drivers installed, no exclamation mark. HDD sharing enabled.

    with the same procedure in WinME it register the IP address I want. But Win2k is not doing what it's told.

    At the moment PC is stand alone ready to be plug into another PC. Both at home, trying to make simple network. In winME the network is fine, perfect. Only win2k can't work.

    Best regards
    Fa Cheng CHIN
Ask a new question

Read More

TCP/IP Windows