Discussion Locked

Workstations interoperating w/NT & Linux

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Linux is my DNS, NT is my PDC, Proxy. I recently have installed NIC in Linux for local IP, NT has 1 NIC for local & valid. Linux (valid IP) & NT (valid IP) share common gateway. THEY CAN PING EACH OTHER.

Problem. workstations can ping & log to NT but not w/ Linux using local IP. Linux also cannot ping local IPs, request timeout error. All WS uses Linux as it's DNS & gateway.

Requirement. Provide troubleshooting procedures or analysis, most importantly, solution.

10 replies

by mcessna

I'm trying to figure out yout topology, is the linux box behind the NT proxy? Does the Linux have two NIC one public, one private? I think your problem has to do with your gateway and routing but I need to know exactly how the boxes are interconnected

by pinoy

Linux is DNS, so it must be outside of proxy. 2 NIC?....i said so. Problem w/ gateway...i don't think so coz NT & Linux can communicate well.

by timgray

First off, you need to have samba running. Configure samba on the Linux box to a netbios name, create that machine account on your PDC and then set the linux box to authenticate to the domain. now, you have to do some really really tricky changes inthe linux-samba to get the samba box to authinticate the domain users on it'sself.
Email me (gray.tim@broadband.att.com) and I'll send you my config files.

if you dont know linux and samba backwards and in your sleep, you will not get this working.

by pinoy

I have samba inside my network.....that's not my concern now. tnx anyway.

by mckaytech

It sounds like you have a gateway issue. I'm going to assume the IP addresses are fine. Here's how the gateway addresses should work:
Linux box - gateway should be the internal IP on the Proxy server
NT box - gateway on the internal IP should beset to the external IP and the external set to the ISP gateway
Workstations - gateway should be set to the internal IP on the Proxy server; DNS should be set to the internal address of the Linux box.
You do NOT need Samba for this situation - it is for printer and file sharing, not routing of IP packets.

paul

by pinoy

I don't think gateway is the issue. I said NT & Linux can PING each other.

by hugevlad

There is not enough information, but I try to help.
1. All WS uses Linux as DNS & gateway, but can`t log into & ping using local IP. Thus, DNS & GW assigned to external (valid) IP of Linux mashine. I am right ?
2. It is possible to log into linux-box using external (valid) IP ? I think, yes, because DNS works.
3. Look like, that internal (local) IP on linux-box not configured properly.
-----------
Try step-by-step:
1. Issue 'ifconfig' on linux-box and be sure, that either interfaces are up, have correct IP and netmask.
2. Issue 'route' on linux-box. Check, that route table has entry for external network (with valid IP) and local network. For linux kernel before 2.2.x you need add this route manualy. 2.2.x make this automaticaly.
3.Use 'traceroute ' on linux box to find out where ICMP packets lost. Then try from other side: use tracert on Win-station to check this problem.

WIth best regards,
Vlad
mailto:hugevlad@yahoo.com

by pinoy

I think you're right in almost all, except that i don't know where you're heading me. I need a solution.

by nold

I supposed your problem started w/Linux when you installed the LAN NICard. I have done a couple of installation in Linux that
point out to thesame mistake. Especially if you have same make & model NIC, in Linux. for valid and local IP.

Traceroute each card to see where packets are going. I think you're connected in a switch, both LAN & valid, since you can ping NT & Linux wether it be local or valid.

Procedure:
In Linux
1. Traceroute each NIC, there's a possibility that the local NIC sends packets to a valid IP, that's why you have the error REQUEST TIMEOUT. If that happens you have a misconfigured NIC.
2. Look at your NIC's config--ifconfig. Make sure that eth0 is used for the LAN.
3. Make sure your eth1 that uses your valid IP.
5. Now traceroute each NIC, your local NIC should not use the gateway of the valid IP.
6. Then finally ping. there should be no error.

Good Luck!

This discussion is closed to new replies.