spbanzaca
New member
My apologies for the length of this post but I figure it's been a thorn in my side and I figured if I put everything in there that we've discovered so far, it might help someone shed some light on what we might be missing.
Situation is: we support an offsite office that works in another building. The work on the network in this building they are situated in. They only use the network to VPN back in our network. There are 5 people in this office. They have 2 printers which are set up on the office network they work in. They have printing and scanning capabilities. Of these 5 people, only two of then work in the office all the time. The other 3 people split time between that offsite office and a local hospital(we support a large heath care company).
They use a Dell 2150 MFP to print and scan. Each person is set up to use the address book on the printer to scan to a folder on their laptops to the C drive named "directscan". Everyone in the office is set up the same exact way.
The 3 people who go to the hospital were able to scan on the network at their offsite office. When each of them went to this hospital, and connected to the hospital's public network and then returned to the offsite office and connected back to their private network the now receive an SMB error 031-528: Server Not Found.
In this case, the "server" is actually the laptop. When the printer begins it's attempt to scan, it's looking for the laptop name which is inputted into the "Server address" field in the Address Book on the printer. It appears to time out while looking for the "server". Something is preventing it from finding it. The funny thing is that the 3 end users have in common is that scanning suddenly stopped after going to the hospital office and connecting to their network. Something prevents them from scanning when they return to the offsite office.
They don't scan at the at the hospital. Only when they return to their office. We were thinking there is some kind of setting getting turned on in the laptop somewhere that is preventing the printer from seeing the server(laptop).
We have tested by imaging a new laptop for one end user. Sending her to the offsite office and testing scanning. She was able to scan ALL day. Next day she took the laptop to the hospital. She returned to the offsite office the day after and scanning stopped working.
We also tested at the offsite office on one of our laptop and creating a profile for one of the end user's to scan on that wasn't currently on her laptop, and she was able to scan on her profile on our laptop.
We cannot nail down what is stopping the printer from seeing the laptop. Anyone have a thought on what it could be or what it is we might be missing???
It certainly would be greatly appreciated....Thanks...
Situation is: we support an offsite office that works in another building. The work on the network in this building they are situated in. They only use the network to VPN back in our network. There are 5 people in this office. They have 2 printers which are set up on the office network they work in. They have printing and scanning capabilities. Of these 5 people, only two of then work in the office all the time. The other 3 people split time between that offsite office and a local hospital(we support a large heath care company).
They use a Dell 2150 MFP to print and scan. Each person is set up to use the address book on the printer to scan to a folder on their laptops to the C drive named "directscan". Everyone in the office is set up the same exact way.
The 3 people who go to the hospital were able to scan on the network at their offsite office. When each of them went to this hospital, and connected to the hospital's public network and then returned to the offsite office and connected back to their private network the now receive an SMB error 031-528: Server Not Found.
In this case, the "server" is actually the laptop. When the printer begins it's attempt to scan, it's looking for the laptop name which is inputted into the "Server address" field in the Address Book on the printer. It appears to time out while looking for the "server". Something is preventing it from finding it. The funny thing is that the 3 end users have in common is that scanning suddenly stopped after going to the hospital office and connecting to their network. Something prevents them from scanning when they return to the offsite office.
They don't scan at the at the hospital. Only when they return to their office. We were thinking there is some kind of setting getting turned on in the laptop somewhere that is preventing the printer from seeing the server(laptop).
We have tested by imaging a new laptop for one end user. Sending her to the offsite office and testing scanning. She was able to scan ALL day. Next day she took the laptop to the hospital. She returned to the offsite office the day after and scanning stopped working.
We also tested at the offsite office on one of our laptop and creating a profile for one of the end user's to scan on that wasn't currently on her laptop, and she was able to scan on her profile on our laptop.
We cannot nail down what is stopping the printer from seeing the laptop. Anyone have a thought on what it could be or what it is we might be missing???
It certainly would be greatly appreciated....Thanks...
My Computer
- Computer type
- PC/Desktop
- OS
- 64
