Windows 2012 / 8 SMB Connection problem

[guddler]

Before I waste another night of my life on this c*cking thing, can anyone shed some light on this for me please?

I had a Windows Server 2008 R2 box that I just upgraded to 2012 and all went pretty well. I transferred my raid disks over to the new box and it all just came up. My shares are all there but my Windows 8 PC cannot connect to them. I get the message: "The device or resource (BRAIN) is not set up to accept connections on port "The
File and printer sharing (SMB)".

BRAIN is the name of my server (the old one is PINKY

)

Anyway, SO, firewall is not enabled (yet!). I've done a bunch of reading and understand that SMB is now at version 3 in Server 2012 so that may cause problems with my Windows 7 or below clients, but Windows 8 is also v3 - so what gives???

Any ideas warmly welcome. Apart from go back to 2008R2 or god forbid, Linux!

Ta,

Martin.

guddler2013-06-13 21:09:43

 

[trm]

Has the Win8 PC ever been subject to any Group Policies?

Glad the RAID came over. I knew it does, but it's still a stressful one

 

[guddler]

Good question!

Not this partition, no. It was my other Windows 8 partition I borked with AD (which I do realise is not the same as Group Policy).

I did have a look in there just now and didn't see anything that screamed FIXME at me.

Having a nose at an article on SMB dialect negotiation at the moment, but I'm somewhat puzzled as I would think between 2012 and 8, it ought to just work. Unless the server has picked up a weird state due to the upgrade.

 

[trm]

If you want to do a Wireshark sniff I'll happily have a look at the SMB nego. Even though I've turned into an app layer wuss I can still decode a pcap with a hex editor

 

[guddler]

Never mind - WHAT A DICK (me, not you!!!)

I just looked at the message again and had a moment of clarity. It does help if I tick the box entitled "File and Printer Sharing for Microsoft Networks" on the virtual network adapter that Hyper-V creates, doesn't it!!

And that was a left-over from the upgrade. I had to remove the virtual Switch / NIC and re-add it using Hyper-V to get the Server to use it's proper static IP rather than claiming a DHCP served one as well.

I need sleep

 

[Alpha1]

What's event viewer saying? And have you got an SMBDirect/RDMA/iWARP/Infiniband Ethernet controller in your new shiny piece of kit? That might be causing an issue as it will take advantage of it automatically.

SMB 3.0 FTW btw

Going into a project with this at work in the next month for Windows Storage Spaces and HyperV 3.0

 

[trm]

Hehe. A fix is a fix. It won't be the first time something has gone wrong because SMB isn't bound to the interface

 

[guddler]

It sounds better when you say it that way

Time for some more scrumpy I think!

 

[trm]

Time for some more scrumpy I think!

There's your problem!

 

[guddler]

Nah!

SO, now the question is "what to do with the old Microserver??"

The obvious answer is to sell it, but that's not going to happen while the current offer is on.

Shame it's AMD or I could have a go at putting OS X on it.

 

[Alpha1]

Ah yes HyperV is much improved but i'm sure it creates that virtual nic in 2008 R2 also

 

[guddler]

Yeah, that's where it was there from - but there was something odd that happened in the upgrade. In 2008R2 there was the physical NIC that had nothing defined except the virtual switch. No IP, nothing. And then the virtual NIC that you assigned the IP and everything else to. That's normal as it provides a layer of abstraction from the actual hardware for Hyper-V. Like you say, that happens when you install the Hyper-V role.

For some odd reason, after the upgrade it got a bit messed up and the virtual NIC still had all it's static info correctly, but the physical NIC decided it was going to pick up a DHCP allocated address as well. Maybe that's a new feature in Hyper-V now that you don't need to dedicated the physical NIC?

Problem was, I didn't notice it until early hours of this morning when I was trying to work out why I couldn't get to any of my web sites from the outside world. It was because they were being served up on the DHCP IP, not the static one I'd let through my firewall. So to fix it, I deleted the virtual NIC and put it back in again, problem solved, but I didn't think to check that File & Printer sharing was enabled

 

[guddler]

In fairness the upgrade was really smooth. I thought the only things that needed re-installing were IIS and MySQL. In reality it was only IIS. The reason MySQL wouldn't run was because it's config file was on the RAID disks that were still in the old server

By the time I realised that, 24 hours later I'd already ripped MySQL out in favour of SQL Server Express!