Solved

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

Posted on 2002-05-27
14
360 Views
Last Modified: 2013-12-28
Hi,

I have this funny problem on a NT4.0 Server where I can get an IP from the DHCP server yet I can't ping it or any other computers on the network. I tried putting in a static IP and same problem. Can't ping any computers. I can do a ipconfig /release and ipconfig /renew without any problem. With NetBEUI protocol installed, I can connect to other Server and workstations. Here is a list of what I have done to tried fixing this problem without success.

- Remove and reinstall tcp/ip.
- Reinstall Service Pack6
- Replaced the Network Card.
- Remove all protocols and then reinstall tcp/ip as well as with netbui.

- Tried different RJ45 Jacks and cables that is known to be working.

- Tried different HuBs.


Any help would be greatly appreciated.

Majah.




0
Comment
Question by:majah
  • 3
  • 2
  • 2
  • +5
14 Comments
 
LVL 6

Expert Comment

by:sstouk
ID: 7037826
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?




0
 

Author Comment

by:majah
ID: 7038007
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
0
 
LVL 63

Expert Comment

by:SysExpert
ID: 7038251
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 !
0
 

Author Comment

by:majah
ID: 7038275
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.
0
 
LVL 6

Expert Comment

by:sstouk
ID: 7039057
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.


0
 

Expert Comment

by:onis
ID: 7039068
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!
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 63

Expert Comment

by:SysExpert
ID: 7040401
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 !
0
 
LVL 2

Expert Comment

by:GeertJon
ID: 7044908
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
0
 

Author Comment

by:majah
ID: 7045386
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.
0
 
LVL 1

Expert Comment

by:reason100
ID: 7052017
If I told you now that the problem is with ZoneAlarm would you give me credit and the points? :-) Just kidding.
0
 
LVL 24

Expert Comment

by:SunBow
ID: 7064124
> - 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
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 11119062
PAQed, with points refunded (200)
ee_ai_construct - CS Mod
0

Featured Post

Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

Join & Write a Comment

For a variety of reasons, it sometimes makes sense to reboot a Windows-based computer on a regular, perhaps daily basis. This "cures" a lot of ills by resetting processes, flushing caches, refreshing memory, and reestablish network connections. In a…
Recently Microsoft released a brand new function called CONCAT. It's supposed to replace its predecessor CONCATENATE. But how does it work? And what's new? In this article, we take a closer look at all of this - we even included an exercise file for…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

746 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now