interfacing problem

[sry]

Hi! Gurus,
I have a typical problem for u all.
assume

UNIX M/C -----------
ip address 203.197.218.12
gateway 203.197.218.49 , 192.168.205.1
|
|
|
NT m/c

ip address 192.168.205.1 , 203.197.218.13
gateway 203.197.218.49

NT m/c is on 192.168.205.0 subnet
UNIX 203.197.218.0 ''

when i ping from NT to unix it works but reverse to NT from unix pinging 192.168.205.1 does not work. When i ping Second ip address of NT 203.197.218.13 , it does work.
Anykind of help is highly appreciable.
shriram

 

[KarveR]

The simple part of the answer is both the unix and NT boxes have a common subnet IP 203.197.218.* which both will use freely as the packets are directly routable across a common gateway.
You will need to look at the routing tables for both NT and Unix to get an idea of whether these ip's ( 203.197.218.12 - > 192.168.205.1) can actually see each other.
Both will require mods to the routing table or the gateway router itself to enable cross-subnet traffic.
______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.

 

[sry]

Dear Karve
Thanks for reply.
i am little bit new to UNIX. would u pl. elobarate me in steps.
thanks.
shriram

 

[syadav]

Thanx. I , my self,solve this problem.
Basically it was routing problem.
i removed all the entries from routing table of the email server.
and allowed to dynamic routing to update it automatically.
second, i enabled ip routing from the NT server.
it works well.
but still pinging from UNIX m/c to NT or any m/c takes lots of time.
write u back if i find any solution.
sry

 

[KarveR]

Sorry, been away for a while, glad you found the answer.

For the hosts to identigy each other check out the /etc/resolv.conf file.

If they are enetered into this file they should resolve the route alot faster. ______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.