NT4 TCP/IP Problem: Can't Ping DHCP Server but can get IP.

Please tell the following details:

1) Can you ping Your Own IP?
2) Can You ping the Gateway IP?


3) Could you dump the result of the "ipconfig /all" command here? So that your configuration would be available?

4) By "I can connect to other Wirkstations" do you mean you can map drives with the "net use"  command and specifying the Host name?

You should be able to do it OK, if you have NetBEUI Installed.
But can you do it by specifying IP address..?? You should not be able to do it by IP address, only by the Host name.

5) Also post here the Addresses in your HOSTS file on the local system:
c:\winnt\system32\Drivers\ETC\HOSTS
What custom entries do you have there?

6) If it is only the ping problem and not the IP configuration, as you discribed it, then you should be able to browse the Internet from this system. Can you confirm this?

Hi sstouk,

The Server works perfectly fine with just the NetBeui protocol installed. It can map drives from the other servers and Clients can see and map this Server's share folders.

I can only ping itself. It can't ping the router or any other TCP/IP devices on the network. I have also put in static IP address with the same result.

I can't browse the internet.

Here is the ipconfig /all settings:

DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.254
DNS Servers . . . . . . . . . . . : 192.168.0.254
Lease Obtained. . . . . . . . . . : Monday, May 27, 2002 2:54:26 PM
Lease Expires . . . . . . . . . . : Monday, June 10, 2002 2:54:26 PM

Please let me know if you need further information.

Majah

1) Get the newest NIC drivers for your NIC.

2) reapply sp6a

3) Check the DHCP server for bad IP addresses or other problems.

4) Check the 3 event logs on the server and Client for anything unusual.

Are there anyother computers on the LAN ?

Are they working OK ?

I hope this helps !

Hi Sysexpert,

- Different NICs have been tried with the latest drivers.

- SP6a has been reapply many times

- Tried different static IPs

- Nothing usual in the Eventlog

- Other computers on the Network work fine with TCP/IP Protocol. Another NT40 Server on the same network is also working fine with TCP/IP.

Please let me know if you need further info. Thanks

Majah.

What about other Systems on your network?
Do they work OK?
Looks like you are using a router with Cable or ADSL Service.

If it is true, then Your Router should be the Default Gateway and if Your router has an address of 192.168.0.254, then Your default Gateway should be the same, because it is the router, which gives you DHCP address.

Try it.

Change your default gateway to 192.168.0.254 and let's see what happens.
Do it statically.

Have you tried a changing the port on the hub or switch you're connected to?
Or maybe you could change your network cable.

I know it shouldn't be any of those options because you shouldn't be able to obtain an IP adress from the DHCP server. But a few months ago I had a problem similar to yours and it turned out to be a faulty cable. Go figure.

Good luck!

1) Check the IRQ of the NIC, and make sure it is not on any IRQ that is already being used ( 2,9 especially).

2) Try putting the NIC in a different slot.

3) You have tried just about everything, but I would try again, with a different brand NIC. Make sure to totally remove TCP/IP and any relevant registry entries from previous NICs.

I hope this helps !

I did not see the question in the history, but are you sure that you verified if the subnet mask is the same on the failing server as well as the other working servers ?
since Netbui is functioning, I do not suspect the driver to be causing this problem.

GeertJon

Hi All,

I finally found out what the problem was. ZoneAlarm was cause of the problem. Eventhough ZoneAlarm was disabled and not use for sometime, somehow by removing the ZoneAlarm, I solved the problem. Thanks to all who tried to help.

Majah.

If I told you now that the problem is with ZoneAlarm would you give me credit and the points? :-) Just kidding.

> - Remove and reinstall tcp/ip.
This was the answer.
For NT you should run NetBios not NetBeui - at all ends
This does not affect pinging. Just other networking. ZA was not responsible. The stack S/W must be loaded in proper sequence. Likely, the sequence of the upgrade path wa out-of sequence for awhile. Believe what you want