Unable to Connect to Local Network on SLES11

We bought a Fujitsu server preinstalled with SuSE Linux Enterprise Server 11 a few months back and we are now trying to connect it to our local network. The server is connected to our local network by a Cisco Small Business switch. The server has been set to have a static IP of 10.100.200.50. We have tried to ping the server from our desktop computers on the network and the ping request always times out. If we try to ping our computers from the server the same thing happens. As of right now the the only IP that will respond to a ping request from the server is 10.100.200.31 which is our DNS server. Why might this be happening and how would we go about fixing this so that we can get the server on our network?

Thanks,
John
lbsiAsked:
Who is Participating?
 
lbsiAuthor Commented:
We have actually fixed the connectivity issue. It seems the ethernet card on the eth0 interface may be faulty. I switched to using the eth1 interface and can now ping other servers on the network and the broadband gateway. As for the internet connection issue, we also had the Name Servers and Domain Search List configured incorrectly under the network settings. It wasn't reaching out to our ISP for requests outside of our network. Once we added the ISP's DNS server IP we were able to connect to the internet. Thank you all for your help though!
0
 
iammorrisonCommented:
Is there anything on the network managing the DHCP role? Have you tried putting a static address on the test workstation as well?
0
 
aarieCommented:
Are the servers and clients in the same subnet?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

 
lbsiAuthor Commented:
There is a domain server managing the DHCP role. All IPs 10.100.200.100 and above are handled by DHCP while all others below are static. All servers and clients are in the same subnet 10.100.200.0.
0
 
aarieCommented:
Does the suse server use the correct netmask? If not, it may try to send the icmp echo reply/request messages to it's gateway.

Also, what kind of clients are you using? Windows, unix/linux, mac? Windows machines usually don't answer to icmp echo requests (ping) and need to have that enabled in their firewall settings. That wouldn't explain why a ping from client to server is not working though.
0
 
lbsiAuthor Commented:
We are using the netmask 255.255.255.0 and have even tried using 255.255.0.0 but there was no change.

We are using Windows clients, but we are even unable to ping other servers on our network running Windows Server 2008 from the SuSE Linux server.
0
 
iammorrisonCommented:
Was it a brand new Cisco switch, or an existing one? And is ping (icmp) the only issue you are having?
0
 
lbsiAuthor Commented:
The Cisco switch has been in place since before we bought the server. Outside of trying to ping the server, it is unable to connect to the internet as well even though our broadband gateway is also on the network. We have tried pinging the gateway and the requests will time out.
0
 
iammorrisonCommented:
from the server, can you ping the switch? Do you have access to it? It sounds like the interface that server is on may be on a different vlan
0
 
d0ughb0yPresident / CEOCommented:
Presuming that you can ping Windows clients (and servers) from each other without a problem. Is that correct?

Is there any possibility that there is a software firewall of some kind running on the SUSE box?
0
 
aarieCommented:
If you connect another device (one of which you know it can connect to the internet) to the switchport the suse server is on, does that other device still work?
0
 
lbsiAuthor Commented:
I have tried pinging the switch IP, I was able to find it thankfully, but the SuSE server still times out. It doesn't make sense though how the Linux server would be able to ping 10.100.200.31, our DNS server, if it was on a separate vlan. 10.100.200.31 is the only IP that the SuSE server can ping without timing out.

We are able to ping between other servers and clients without any issues, just not the SuSE server. I made sure to disable the firewall used by the SuSE server but it had no effect.

I connected a laptop to the switchport the SuSE server was on and was able to get internet access and access to the local network.
0
 
aarieCommented:
If you have the suse server ping a client machine while you're running a sniffer trace on that client (you may want to disable the firewall of the client), do you see the icmp echo request packets coming into the client machine?
0
 
lbsiAuthor Commented:
Even though the other solutions listed helped us leading up to finding our answer, they did not actually solve the problem that was at hand.
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.

All Courses

From novice to tech pro — start learning today.