3

Server networking suddenly flaky

view full story
linux-howto

http://www.linuxquestions.org – I've had a server running for over a year and it's been very stable. Suddenly (no config or software changes) it's behaving oddly. If I perform a network related activity, it appears to effect other separate network functions. Example: I get onto the machine using realvnc server and suddenly port 80 goes down, or I can access port 443 inside the network but not externally, or I can get to 443 but not 80. The server has two network cards. Switching to the second card appears to have had no effect. I also tried rebooting, switching in a new network cable, bouncing the network card (which d (HowTos)

dayu's picture
Submitted by dayu on 08/25/2010 – Made popular on 08/25/2010

Stories similar to Server networking suddenly flaky

I have a win2008 Server with 4 network ports (A,B,C and D) where only 1 port A is connected to the LAN (192.168.0.0/24). The other 3 ports (B,C and D) are not in use.

I have another PC want to join the same LAN(192.168.0.0/24) by connecting the pc's network port P to one of those 3 unused network ports (I am using network port B in this case) on win2008 server.

Hello:

I'm using Suse 11 as a router. The machine is a thin blade with room for only one card: a network card. I'm using the network port on the motherboard as my external network port, and the network card as my local port. Everything works fine.

I'm thinking of replacing my network card with a four port card:

I had ssh running on my LAN server. Suddenly (not sure what I did), I cannot access the LAN server via ssh. When I try, it just hangs for a while with no response and finally comes out with a timed out message.

ssh: connect to host 192.168.1.50 port 22: Connection timed out

As I recall, maybe I got into some trouble trying to install phpmyadmin and pgmyadmin.

Lets say there is Machine A (Ubuntu) in Network A and Machine B in Network B. There is also Machine C (Windows 7) in Network B and I can access it through RDP from Machine A. What I need is to be able to reach Machine B from Machine A (i.e. can ping it, connect to arbitrary port, etc). How can I manage something like this?

PS: Network B is a dmz, i.e.

I have 2 servers running CentOS 6

I have a server A, that has 2 network cards. eth0 is a private test network. eth1 is the corporate network, where a proxy server must be used to access the internet. On this server I use

export http_proxy=http://proxyserver:3128/

and am able to access the internet.

I have a server B that has 1 network card.

Hi All,

I have just setup a webserver running on a linux box. This server has 2 ethernet cards and only 1 is in used now. eg. 192.168.10.1 is my server IP. All users from 192.168.10.X can access my webserver. However, users from another LAN 10.10.10.X are not able to access my webserver. They can ping and receive response from my server yet web browing is not possible.

A funny thing happened this afternoon.

After a restart of my home server (that I use as a testing environment for websites and as a backup for files on the other computers on the network) which is running Server 2008 R2, I am now unable to access the server or any of the shares on the server from any of the other computers on the network.

I was able too before, I haven't to my knowledge changed

I have some troubles with my server! After I asked for support, I get the following answer:

You can use the serial port to reset your network configuration.

I have a client machine with Ubuntu Oneiric Ocelot (11.10) installed on it and a cable for serial access with 9 pins in a head and a network connector in the other.

This is the first time I am faced with routing and it seems I have hit a dead end.