I installed a Netgear FVS318 (VPN Firewall) into existing network. Old/existing IP scheme was 192.168.1.x.
New FVS318 IP scheme is 192.168.45.x.
I therefore changed all PC's + other equipment to match subnet and all is well.
However, I have a Kyocera KM-3050 multi function printer, scanner, copier, fax, and it was 192.168.1.101 before the install. I changed it to 192.168.45.101 after the install to conform and all works (printing), however, 'Scan to folder' (scans to a shared folder on a PC in the network via address book with IP address via SMB (Port 139) which worked before IP change and VPN installation now fails with error 2101 (invalid path). All IP's are now conforming to the new subnet (192.168.45.x)
Is there ANY reason the SMB scan to function would fail as it worked before the install of the FVS318?
I disable the firewall, does it work?<--NOPE
I power cycled the printer?<--NO DIFFERENCE
I am sending to the IP from the printer?<--Also tried HOST NAME, no difference
IP, subnet, gateway all correct (can print fine from 6 computers to KM-3050)
Disabled firewall on all Windows 7 PC's, makes no difference.
Yes, can ping the device.
Digging around, back to 2002:
(On Broadband Reports)
Re: FVS318 auto blocking SMB?
I'm stumped. directory services and SMB use 445 and 139. Just to make sure I wasn't losing it, I used ethereal and sure enough, my attempts to bring up my server were hitting 445 for directory services and 139 for SMB, but very little was coming back beyond a single SMB Negotiate Response.
Any ideas? My security logs show nothing actively being blocked during my connection attempts.
Answer was:
Never tried it, but you may have to forward those ports back to your machine (in case it's a handshake-type connection).
Just a guess.
"-)
So, yesterday I called Kyocera support hotline, they said SMB shold be Port 445 on KM-3050, NOT 139 (he said 445 is for Windows 7, 139 is for all other OS's) [I changed it, no difference], and to check time sync on all equipment (to be within 5 minutes of each other). Makes no difference.
I am stumped, it all workd before, an onsite tech was there for 2+ hours on Wednesday this week, he plugged his laptop into the printer and scanned to it (after configuring of course), but again the question is, why, what changed, and it worked before with only an IP change of ll equipment to x.x.45.x from x.x.1.x....???
New FVS318 IP scheme is 192.168.45.x.
I therefore changed all PC's + other equipment to match subnet and all is well.
However, I have a Kyocera KM-3050 multi function printer, scanner, copier, fax, and it was 192.168.1.101 before the install. I changed it to 192.168.45.101 after the install to conform and all works (printing), however, 'Scan to folder' (scans to a shared folder on a PC in the network via address book with IP address via SMB (Port 139) which worked before IP change and VPN installation now fails with error 2101 (invalid path). All IP's are now conforming to the new subnet (192.168.45.x)
Is there ANY reason the SMB scan to function would fail as it worked before the install of the FVS318?
I disable the firewall, does it work?<--NOPE
I power cycled the printer?<--NO DIFFERENCE
I am sending to the IP from the printer?<--Also tried HOST NAME, no difference
IP, subnet, gateway all correct (can print fine from 6 computers to KM-3050)
Disabled firewall on all Windows 7 PC's, makes no difference.
Yes, can ping the device.
Digging around, back to 2002:
(On Broadband Reports)
Re: FVS318 auto blocking SMB?
I'm stumped. directory services and SMB use 445 and 139. Just to make sure I wasn't losing it, I used ethereal and sure enough, my attempts to bring up my server were hitting 445 for directory services and 139 for SMB, but very little was coming back beyond a single SMB Negotiate Response.
Any ideas? My security logs show nothing actively being blocked during my connection attempts.
Answer was:
Never tried it, but you may have to forward those ports back to your machine (in case it's a handshake-type connection).
Just a guess.
"-)
So, yesterday I called Kyocera support hotline, they said SMB shold be Port 445 on KM-3050, NOT 139 (he said 445 is for Windows 7, 139 is for all other OS's) [I changed it, no difference], and to check time sync on all equipment (to be within 5 minutes of each other). Makes no difference.
I am stumped, it all workd before, an onsite tech was there for 2+ hours on Wednesday this week, he plugged his laptop into the printer and scanned to it (after configuring of course), but again the question is, why, what changed, and it worked before with only an IP change of ll equipment to x.x.45.x from x.x.1.x....???
Comment