HP Server no network link to Mikrotik router

[tek9]

Hi All.
Interesting problem here.
I just setup a new HP ML350 Gen10 server for a client. Loaded Server 2016 Standard as a Hyper-V Hypervisor and installed the HP SPP to get the latest drivers etc, then provisioned a single VM running another instance of Server 2016 Standard to be his DC and file server. Very small accountant client. I set static IPs for the Hypervisor and the VM and made the DC the DHCP and DNS server etc.
All worked fine in my office when setting it all up, connected to an Untangle router initially, and then when I needed to setup the DHCP settings on the VM, and they were in a different range than the Untangle, I connected a temporary Zyxel router I had lying around and used that as the gateway to get everything setup and all went well.
Next day I deliver it to the client who's using a MikroTik router provided a company doing his web filtering. This company manages the router (connected to a cable modem provided by the ISP) and only allows a white-list of certain sites to be accessed, and all the computers on the network need to have Internet Explorer Proxy settings configured to go through this company's proxy in order to get online.
The basic network is setup very simple: ISP modem > Mikrotik router 4 ports connected to the 4 jacks in the wall that go around the 2-room office. The jack in the office is connected to a dumb Netgear Prosafe gigabit switch which connects the computers, printer and phones in that room. When I tried to connect the new server to the Netgear switch it would not recognize the cable connection. No lights on the switch nor the server NIC ports. Tried different ports on the switch, different cables, and also tried all 4 server ports. All dark. If I connected the iLO port, it DID light up and get a connection.
I tried connecting the server directly to the wall jack which is going to the Mikrotik, bypassing the switch, but it still didn't light up. I went into the BIOS settings and it said that there was no connection, tried all the ports, refreshing the status in between, with no change.
Now if I took the Mikrotik out of the equation, and connected this wall jack directly to the cable modem, the light on the server NIC lit up immediately and I was able to get online from the Hypervisor once I changed the NIC settings away from a static IP. When I put them Mikrotik back in, same thing happened: no lights and no connection.
I spoke to the filtering company and they didn't know what to make of this. They were thinking maybe it was running an older firmware or something, so they sent the client a newer router which was installed today but still nothing doing.
So to break this down: Everything else except for this server works fine on this network with this equipment. Is it because the proxy isn't configured? If so, shouldn't the link light come on at least and the server should recognize a cable being connected?
If it's the router, maybe an issue with port speed and duplex settings, then why would the switch not light up when I connected the server to it?
Any ideas? I'm stumped.

 

[YeOldeStonecat]

So when you plug in the patch cable to the HPs NICs....the LAN status icon stays with a Red X on it? Or just getting the unknown network?
Using the default onboard NICs? Or additional Intels?

 

[tek9]

Using the default onboard NICs, red X, no lights for the physical NICs, as well as the Network light on the front panel of the machine.

 

[SAFCasper]

Strange one.

I would start by ruling things out. Fit a different NIC and see what happens. Take a different switch and see what happens etc

I'm with you on thinking it could be a port speed / duplex mismatch. Shouldn't happen these days with modern hardware and auto-sensing, but I've seen it happen.

 

[nerd2u]

Sure you don't just have a bad cable in the mix somewhere?

Start by confirming cables and connectivity from a laptop to make sure everything is working.

Sent from my SM-G870W using Tapatalk

 

[tek9]

Sure you don't just have a bad cable in the mix somewhere?

Start by confirming cables and connectivity from a laptop to make sure everything is working.

Sent from my SM-G870W using Tapatalk

Pretty sure it's not the cable. Tried three different cables that were working fine for other devices there. Also the same cable, same switch and same router did work when connected to the iLO port on the same server.

 

[Markverhyden]

Which model Prosafe? Some do have management but they are flat by default. Was their a previous server? If so did you look at the settings?

Some ideas to try in no special order.

1. While the Netgear is NOT connected to the Microtik cable up the server with a fixed IP and another box with a fixed IP to the Netgear then test for connectivity.

2. You said they have a proxy. Was the proxy put into the server nic config?

3. Did they make a reservation for the server IP's. White list the MAC's?

4. How was the ILO configured? Static or DHCP? Could you access that service port on the LAN?

5. Have you tried changing the nic driver pack for the 4 port? Are they the same as the ILO port?

6. Toss a copy of Microtik on a desktop with multiple nics and see what happens.

I have a vague recollection of a similar situation but can't find it. Seem to remember the solution involved changing the nic drivers.

 

[tek9]

Which model Prosafe? Some do have management but they are flat by default. Was their a previous server? If so did you look at the settings?

Some ideas to try in no special order.

1. While the Netgear is NOT connected to the Microtik cable up the server with a fixed IP and another box with a fixed IP to the Netgear then test for connectivity.

2. You said they have a proxy. Was the proxy put into the server nic config?

3. Did they make a reservation for the server IP's. White list the MAC's?

4. How was the ILO configured? Static or DHCP? Could you access that service port on the LAN?

5. Have you tried changing the nic driver pack for the 4 port? Are they the same as the ILO port?

6. Toss a copy of Microtik on a desktop with multiple nics and see what happens.

I have a vague recollection of a similar situation but can't find it. Seem to remember the solution involved changing the nic drivers.

It's a plain blue Prosafe box. No management whatsoever.
I was thinking of just connecting the server to the Netgear without the Mikrotik in the mix to see if the link lights up at least. Planning to go there tomorrow to try some of your ideas.
I did not put the proxy into the server's NIC yet. But that only takes effect once Windows loads, so why isn't the server recognizing a connected cable in the BIOS?
No changes were made to accommodate the server in the router settings.
ILO is getting it's address from DHCP. The first NIC port was set to static, but then changed to DHCP with no change.
Did not change the NIC drivers, but again why would it say disconnected in the BIOS?
I'm trying to convince this client to switch to Untangle, so this might actually be working in my favor

 

[YeOldeStonecat]

So just for giggles....if you manually set the speed of the NIC....100 meg full duplex, or even 100 meg half duplex or 10 meg full duplex...just to see if it lights up.

 

[HCHTech]

i had a server with a similar no-connectivity symptom. Turns out the NIC was 10Gb capable, and it's lowest speed was 1Gb. I was trying to connect it to a 10/100 switch = no go. Put in a full gigabit switch and everything worked.

 

[tek9]

i had a server with a similar no-connectivity symptom. Turns out the NIC was 10Gb capable, and it's lowest speed was 1Gb. I was trying to connect it to a 10/100 switch = no go. Put in a full gigabit switch and everything worked.

It is connected to a gigabit switch. In my office it was connected to a 16 port Netgear gigabit dumb switch, and at the client it's connected to the same type of switch, just a 5 port unit.
I plan on going over the there today with a spare switch, router and what not and try swapping things out.
EDIT: You were right! I had mistakenly assumed that it was a Gigabit switch since it looked just like it, and I never sold a Fast Ethernet switch to any client as far as I can remember. Turns out this client had bought this switch on his own, and it was only Fast Ethernet. I didn't know until I went back today and connected my Fluke tester and when I saw it's only pushing 100mbps I checked the switch. Sure enough, it was 10/100. Swapped it for a Gigabit one and it lit up immediately. Thank again.