i’m no Suse expert but have set up 6 fileservers with 10.3 and 12.3. No big problems.
I have a fileserver with 600k documents still running with a board problem - dropping the second drive in the raid, decision has been made to replace it.
Built a new machine and installed 12.3.
so far so good but the network is behaving in a bizarre way. Sometimes I can ping it sometimes not. When pinging from Win7 sometimes doesnt respond, sometimes responds to a couple of pings and then times out.
From the Suse box I can ping my router but not my Win7 box, but that comes and goes, sometimes it works and sometimes not!
The firewall is disabled, if config shows the card and the Ip address. I can ping 127.0.0.1 and the machine itself so TCP is working.
I have replaced all the cabling, set up a new network in the office (just one PC and router) with new cables (and tried known good cables) a new Gigabit switch fresh out of the box and replaced the network card with a new one and been out and bought a new card.
whatever I do the network connection comes and goes. I have created a new network with everything new. I am using fixed IPs with no conflicts. I am desperate !£&@!
i am at my wits end, I have had to cancel my holiday, I was going away on wednesday for Xmas and I have a business critical server about to self destruct that I need to replace ASAP’.
there is no IP conflict, there are only two devices on the network.
Router IP 192.168.1.1
Win 7 IP 192.168.1.5
Opesuse box IP 192.168.1.10
it certainly is a mystery!
on the site I backup every night and sync out to a backup Suse box every hour but you know how it is we only know how good that strategy is until we have to use it! Dont want to find out - lol…
Hi
Sounds like resolving issues (probably the router - has it been rebooted?). Add the ip address and hostname in the windows hosts file and same on the openSUSE box…
changing the hosts file on the Win7 boxes is not an option. There are 55 users on the network + I havent had this problem with the two servers presently running.
I will do this tomorrow. Its evening here. I will think of a way to do this!!!
I’m not a Linux afficianado so you will have to excuse my ignorance. Although I have to say that the OpenSuse boxes I have built have been awesome for document handling. We used to use win server boxes and the Suse boxes kill them for speed and reliabilty.
I’d be inclined to check the arp table on the router, just to check MAC addresses, and also see what is reported on the servers (after trying to ping the other sever from each machine)
On 2014-12-15 21:46, voodooman2 wrote:
>
> deano_ferrari;2683184 Wrote:
>> Run the commands and copy output to a text file, save on a memory stick.
>
> Thanks
>
> I will do that tomorrow.Its evening here and had two twelve hour days on
> this, my mind is boggled!
Understandable. You must have 10 hour sleep before even thinking of this
problem again - no kidding!
You could run “ntop” on a Linux machine listening (passively) on the
network, sometimes it gives interesting info. You can also use
“wireshark” aka “ethereal”, to listen on the network while you do a
ping, see where it reaches or not. Possibly running it on every computer.
I’m curious about your decision to install 12.3, as this release is
already on the list for discontinuation, which was announced on the 5th
of September, for the 4th of January.
I would have used 13.1, which is very mature, has (I think) 10 months of
support left (two months after 13.3 is released is the date), plus an
extra period of 18? months via Evergreen.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
You need to describe what you are using for your DNS and DHCP, that and in combination if you re-used any hardware when you re-built your box, in particular if you re-used your NICs.
Am speculating at the moment that you re-used your NICs and when your re-built now a new install possibly with a different machine name is now associated with your NICs.
If this is the case, then
You need to purge all the leases in your DHCP and allow new leases to be created
You need to wipe clean and re-build the DNS in your network. If you are actually running DNS for your LAN, this isn’t that difficult to do. If you aren’t and are running a Workgroup, then this may be a bit more complicated… You may need to wipe the resolver cache on every machine in your network and allow each to be re-built. <Maybe> the arp caches may need to be re-built, too but usually those are pretty volatile across re-boots.
Or, just install a NIC that has never been used in your re-built machine.
The machine is completely new. It looked like a hardware problem so I fitted a new NIC one out of the box. After many hours I replaced that again with a different make in case it was a compatibility problem, again new out of the box. I never reuse anything its not worth the bother.
DHCP does not matter with fixed IP does it? Dns also does not affect pinging other machines as I ping with the IP.
I used 12.3 because I have used it before and have it on another machine on the network at the same site. The data is synched to the other machine every hour as a live backup as well as an evening backup. I thought by using a release I know I would avoid problems!
Also, I live in the countryside with no ADSL and my internet is over the mobile phone network., so downloading 4.7gb is a risky business. I downloaded it last night and I am planning to install it this morning.
I downloaded and installed V13.2 and it seems to be just the same. This points to a hardware problem.
The onboard network card was reporting buffer full so I disabled it and fitted a new NIC.
I opened yet another brand new network card still in the shrink wrap.
I can ping other devices on the network but when I ping the OpenSuse box I can get successful ping sometimes, other times it times out!
I have added an XP machine to the network and that is giving me the same results. I have been through all the cabling again and replaced the switch with another one - not new this time, but known good.
All I can think of is that there is a mainboard problem of some kind.
Docstore2:/home/user # /sbin/ethtool enp3s6
Settings for enp3s6:
Supported ports: TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>ping 192.168.1.105
Pinging 192.168.1.105 with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.105: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.105:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
I have no idea, I’m thinking to buy a new board the same as the last good box I built? They are still available but I also bought WD RE4 SATA 3 drives and I don’t think I can use them with the old board.
