Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 261
  • Last Modified:

Linux / Windows communication via tcpip

I bring up a linux server and create a new ip as follows

ifconfig eth2 10.14.51.11 netmask 255.255.0.0
route add default gw 10.14.10.10 eth2

I try to connect from Windows and my windows machine can not see the linux server (cant ping it, or putty to it)

So I usually get by by going to the Linux server and ping Windows, i.e.

   ping 10.14.100.2

After I deliver the ping, my Windows server can then usually ping and putty to my linux server.

However, that strategy is not working now

Is there anything stronger than a ping that will clear the path way up ?
0
Los Angeles1
Asked:
Los Angeles1
Advertise Here
3 Solutions
 
Dave BaldwinFixer of ProblemsCommented:
Connecting hasn't really been that easy since DOS days.  You haven't said anything about allowing 'ping' in the Linux firewall or access permissions to any directories on the server.   'putty' requires an active SSH server and a login.  Samba for file-sharing requires the Samba server and access permissions to be set correctly.
0
 
nociSoftware EngineerCommented:
Also verify that netmasks are the same on all equipment in the same LAN.
0
 
ahoffmannCommented:
assuming that no firewalls are involved, did you ensure that you have the same netmask on windows?
best is to use tcpdump to see the traffic send to wire
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Sign Up
Advertise Here
Tackle projects and never again get stuck behind a technical roadblock.
Join Now