NT Server and TCP/IP

[MadMax]

What's the simplest way to make tcp/ip the only protocol for an NT Server 4.0 file server without DHCP? This is a single NT Server lan without internet access. I've got to have a static ip. I'm not having much luck with this. NETBeui works, IPX works...tcp doesn't. It will ping itself but nothing else and nothing else can ping it.

Also w/NT server...This box stopped advertising in "Network Neighborhood". The "Find Computer" search engine DOES see it right away and drive mappings stay valid. What could cause this?



[This message has been edited by MadMax (edited 06-15-99).]

[800XL]

Set your static IP on the server, and pick an appropriate subnet mask. Something in the 192.168.xxx.xxx range, and 255.255.255.0 should work for your subnet mask. Then, all your clients need to be on the same subnet (192.168.yyy.xxx where yyy is the same on all of the machines) and the same subnet mask. Machines on the same network segment must be in the same subnet, and have the same subnet mask. If you just drop in a server in a network with an IP that is not on the correct subnet, it won't answer anything except perhaps itself.

The other problem sounds like it may be related, or it could be a browse master problem. The master browser machine (probably a domain controller) and the machine in question are probably arguing over who is in charge.

[MadMax]

That's what has me scratching my head. This machine has the proper subnet and ip address numbers. I actually have an IP naming convention map for this lan, if you can believe it.

I have never setup an NT server with tcp/ip before. What about WINS, dns, and default gateway settings? Can I leave all of these blank/unselected and still have connectivity with only tcp/ip installed?

I don't know, I may have an issue with the NIC, it won't let me view/edit its properties. Tks for the reply.

[This message has been edited by MadMax (edited 06-15-99).]

[toms111]

You may have a binding problem. Make sure TCP/IP server service is "bound" to your lan adapter.

[800XL]

Just for grins, try setting the default gateway to the address of the NIC in the machine. I've not had this much trouble ever, so you might be onto something with the NIC driver probs. Reinstalling the driver could not hurt either.

[MadMax]

Took out all tcp related components today and reinstalled. Updated the NIC driver and still no luck. Lost all browsing capability in Nieghborhood from clients to server and can't see anyone from server except server. Can still "find" the server and drive mappings are good. Server can ping itself and the loop back address but nothing else. Keep getting "timed out" both ways. I'm really leaning strongly towards "bad NIC" here. I'm going to change it out as soon as I can kick the users off the system.

[This message has been edited by MadMax (edited 06-16-99).]

[MadMax]

Well, I think I have some kind of protocol prob here. I replaced the NIC and the server came back to the Nieghborhood but it still wouldn't ping right. I built a brand new machine (virgin OS) later and jacked it into the net. It wouldn't see(in tcp/ip) any other comp but the server and these two boxes can ping each other but nobody else! What the @#$!@?? The server and the new box have the same nic (Netgear FA310TX) but I also have 3Com(3C905x) and Kingston(KNE100) nics in this network. All of these cards have different adjustments available. How do I force them all to the same specs at 100mbs(speed/duplexing/burst length)?

[MadMax]

Status update: Net Diag (IPX) is successful to/from every box. Three of these boxes won't ping (TXP/IP) anyone but themselves.

TCP/IP in the prob boxes is identical to like configured boxes that ping successfully. Ruled out cables with good boxes. Ruled out hub ports with good boxes.
Net Diag rules out bad NICs. It's gotta be a config issue, right?
What else can I do to further isolate this problem? Anyone, anyone, Bueller, Bueller.......?

[toms111]

Are all NIC's (and drivers) the same. I have seen some quirky problems with NIC drivers. Some of the worst are on W98 upgrade disk. ie one protocol works but others don't. Try putting a card that properly pings (along with working driver)into a box that doesn't ping.

[This message has been edited by toms111 (edited 06-17-99).]

[MadMax]

No, the NICs are not all the same. I've got 3Com and Netgear. The drivers are all the lastest from the web. I have this lurking feeling that it is something I am doing/not doing in my configs. The NT box is the one I'm most concerned about as I have the least amount of experience with that OS and tcp.

tks

[800XL]

If you can't ping the IP address of a machine, it most likely means there is a config problem on one of the two machines. I would assume that because you can ping between two of your clients, that pins the problem on the NT box, sort of. It has been a while since I dealt with a network not connected to the internet, but I don't recall anything special you would have to do. At worst, you might need a hosts file on the clients to help them find the server by name. The whole problem seems very puzzling.

Here is an example of how I've configured things in the past:

Server
IP: 192.168.0.10
Netmask: 255.255.255.0
Gateway: none
DNS disabled
WINS blank

Client
IP: 192.168.0.20
Netmask: 255.255.255.0
Gateway: none
DNS disabled
WINS blank

That setup, with a flat network (no routers, all machines on the same hub or group of hubs) should allow both machines to ping each other. They might have problems connecting by name without a hosts file because of the lack of WINS or DNS, but ping should work. Is there any Gateway or router on this LAN that could be complicating matters? If the clients are all setup to use some gateway, and that gateway can't figure out how to route their replies back to the server, it would explain the problem.

[MadMax]

There is a router functioning as an internet gateway to an isdn line, but it doesn't route any traffic internal to the lan. It's just another static ip to the lan.

That simple config you posted is similar to mine. The only diff is this:

When default gateway is left blank the error is "???? address not found" (I'm doing this from memory because I'm at home right now)and errors out immediately. When the default gateway is set to the NICs address or the routers address the "Request timed out" error shows up after a few seconds of NIC traffic (verified by the xmit/rcv led). What causes the change?

Sample config:

Server
IP: 207.49.116.130
Netmask: 255.255.255.224
Gateway: none or (207.49.116.130) or (router ip)
DNS disabled
WINS blank

Client
IP: 207.49.116.125
Netmask: 255.255.255.224
Gateway: (router ip)
DNS disabled
WINS blank

I have seen some sites that indicate NT might keep some bogus registry keys active from a network setting that has been messed up and then removed. Is there any truth to this? If so, what's to be done? Do you think this might be my issue?

Thanks for your help, truly. This problem is frustrating and it's nice to know that all the good people at the SysOpt BBS are there to help!

[This message has been edited by MadMax (edited 06-17-99).]

[800XL]

Hrm, freaky. The one thing there that jumped out at me was the Subnet Mask. My TCP/IP is extremely rusty on this subject, but that would seem to indicate that the local subnet is made up of less than the total addresses in the scope of xxx.xxx.xxx.1-255, I think. I'd have to dig out a book on subnetting to figure out what your real scope is, but it seems possible that 130 may be to high. Can you try a number for the server that is less than 128? Perhaps switch it temporarily with one of the working client's IP? Just a thought. I'll see if I can remember how to make sense of a subnet and get back to you.

[MadMax]

Tried with 88 originally. Went through the same troubleshoots with the exact same results.

[Jin Vitas]

So what is the problem? because the first post said that.. the NT server can Find other computers but it just doesn't show up in network neighborhood.. right..