SMB Share Issue with Win8.1

[MiMadreMia87]

I have this issue, I am upgrading some clients from Windows XP to Windows 8.1

The issue am facing is the following:
The PCs communicate with a print server in order to print the documents from the system, the print server is Linux based. In order to enable system printing, the printer has to be shared and has a share name and a specific account has to be configured on the machine.. from the server side the printer is added using the share name and the account defined so basically nothing much to do from the server side

I am unable to print as I used to do before, the PC is listening on required ports and I even turned off firewall and antivirus for testing with no luck.. I ran a Wireshark capture on the client side, everything looks fine until the local PC sends a TCP RST packet.. although the port is open and listening, I even tried to access the printer from another windows machine and it was fine (the only difference is that the windows machine used SMBv2 or 3 while the Server was using SMBv1)

So I tried to dig more into SMBv1 compatibility and found some suggested solutions but with no luck..

 

[MiMadreMia87]

Here is what the capture looks like.. the 10.10.10.62 is the print server..
it just keep repeating this sequence.. I think something has to do with the TCP RST, but the PC is listening on SMB port and I tried accessing the printer from a windows machine and I had no problems

 

[GokAy]

Pardon my confusion,
- there are client PCs (XP, now 8.1)
- a PC running Linux which acts as a print server (printer already shared from Linux)

Which PC has trouble printing? The clients or the server?

May have other questions later

 

[MiMadreMia87]

Pardon my confusion,
- there are client PCs (XP, now 8.1)
- a PC running Linux which acts as a print server (printer already shared from Linux)

Which PC has trouble printing? The clients or the server?

May have other questions later

Oh Finally a reply.. have as much questions as you will!

The clients run XP and are to be upgraded to Win 8.1, and the PC is the testing PC actually
The printer is shared from the Windows machine
Linux server communicates with the client using the printer share name and SMB protocol

The client access a server, and submits a printer order through an oracle based system they use.. this server contacts the linux machines which sends the print order to the printer

so the problem occurs when a print order is sent from the linux machine to the windows 8.1 machine

 

[GokAy]

Hmm, can you browse to the Win8.1 share and see printer that way?

Would this help? Unable to Map Drives from Windows 8 and Server 2012 | Adam Fowler - I.T. From Australia

You may have to change the Win8.1 role in the link (there it was client, in your case server, anyway try as both )

 

[MiMadreMia87]

Already done it with no luck.. but yes it makes since that it is more like a server in my case..
One more thing to try! thank you

 

[MiMadreMia87]

Here is a capture of what happens,
A connection is opened.. SMB negotiated but doesn't go anywhere aferwards.. connection is closed..

 

[MiMadreMia87]

anyone....

 

[GokAy]

I am out of ideas, but is there an update to the Linux server perhaps?

 

[Shadowjk]

I believe the TCP Reset is causing the issue as it is closing the connection. As to why it is doing that? My most likely guess is the incompatible version numbers. Since you are upgrading from XP to 8.1 then you will find the SMB compatibility change.

I would personally strongly look into upgrading the print server software to support the new protocol standard as opposed to trying to get the clients to downgrade.

A normal SMB action should have queries and after the negotiation. Something in the negotiation phase caused the PC to close the connection. This could either be the incompatible software or an issue in generating a tokenID for authentication. More likely the compatibility issue since older machines are still working I believe?



Best Regards,

Josh

 

[MiMadreMia87]

Exactly it should Setup a Session after the: Request, Response
The print server is managed by a different team and there is no way of upgrading it at the moment..
the problem is that Windows 8.1 supports all of the Legacy standards, some of them require to be enabled in specific though.. so I don't think it should be a compatibility problem, but atleast I want to know what part was not agreed during negotiating that resulted in dropping the connection.. this would be the perfect place to start!

Thank you

 

[Shadowjk]

Exactly it should Setup a Session after the: Request, Response
The print server is managed by a different team and there is no way of upgrading it at the moment..
the problem is that Windows 8.1 supports all of the Legacy standards, some of them require to be enabled in specific though.. so I don't think it should be a compatibility problem, but atleast I want to know what part was not agreed during negotiating that resulted in dropping the connection.. this would be the perfect place to start!

Thank you

Well I'd personally get into close contact with that team about changing it. Typically when it comes to client/server relationships, you should make sure the server can meet the requirements of the client. Not the other way round (Unless it is an enforced policy though this is more in Domain environments...). Your clients are the attack vector for your network and is the easiest point of access that an attacker can use to break in.

As for a short term solution, have you read through this to enable the relevant support and see if that allows SMB to continue?

https://support.microsoft.com/en-us/kb/2696547

Best Regards,

Josh

 

[MiMadreMia87]

Any other solutions?
Tried everything suggested on a fresh new installation with no luck.. still the same behaviour

 

[MiMadreMia87]

Bumping ...