On my current Win2003 web server, it is on an isolated segment of the network. We use NAT to connect to the file share on that server. I am attempting to replace that server with a Win2008 server. I can not get the folder share to work on that server. I have configured the security, firewall, etc. the same as the Win2003 server but can not get it to work. I am wondering if something new has been added to Win2008 like maybe it is using new TCP or UDP port then before. Any ideas?

Hello, Do you mean the normal network file and folder sharing or the IIS? May I know what you mean by the sentence "cannot get it to work"? Do you mean that you cannot share the folder, or you cannot access the shared folder? Remotely through the NAT or locally on the same network segment? If you mean that you cannot access the shared folder remotely through NAT, would you please try if you can access it on the same network segment? Please try this, by using the IP address from another computer on the same network segment. I would also double-check if you have made the same setting on the Windows Server 2008 server as that of the old Windows Server 2003 server. Have you joined it to the domain? Have you added the same users into the server? Have you configured the same share and NTFS permissions? Have you given it the same IP address or if you have changed the NAT settings to the new IP address of the newly installed server? Additionally, when you find that you cannot access the shared folder, what the prompt window tells? Besides, regarding the last question. Windows Server 2008 uses the same port 445 as Windows Server 2003. Both of SMB and SMB2 uses the same port so this should not be the cause. You can also try deleting and adding a new entry for the port redirection in NAT to see how it goes (I am assuming that you added this entry yourself). Best regards,Chang Yin

I mean on normal network file share.I can not access the shared folder from my internal network segment thru the NAT. I can access it on the same segment as the user I want to access it so I know that is working fine. I have also tried it with the Firewall off. I'm not sure what other settings I need to check to make sure they are the same. If I turn the firewall off, the folder is set up to share and security has been set for the user I am using, what else would I need to check?From the internal network systems I am trying to use, I get "No network provider accepted the given network path" and "no network was found".Unfortunately I do not control the router so I can not recreate the NAT.Thanks for any help you can provide! This is driving me crazy!

When you connect on the Filer Server do you use host name \\server_name\\Share or IP-address? What if you use server IP, does the connecting computer then see it? Propably the router blocks "netbios" so you can only connect by IP.Btw, can you ping the target machine from the other segment? Henry Eklf :: Just one random IT-guy more.

I connect to the share by ip address then share name.

Hmm... I played with my testserver a little bit and one way to get similar error to yours is to have Shared folders enabled but the "Main" File Server setting disabled :)So you can have folders shared, all the security and share rights configured, but the main File sharing can still be disabled.So you should check:Control Panel -> Network and Sharing CenterFile Sharing: OnThere are more different settings also, maybe you should check them also.You propably have this thing allready checked, but this just came in to my mind :) Henry Eklf :: Just one random IT-guy more.

Yep, checked that as well. If I put the box on our internal network, file sharing works fine. It can connect to it when it is on the same segment on our public side. It's only going thru the router that I can not connect.I know everyone says that Win2008 is using the exact same ports as 2003 but I still think there is a new one being used.

Hello, Would you please also try the following methods? 1. On the Windows Server 2008 which runs as the file server, configure the 'Default gateway' to point to the IP address of the router. 2. Try to see if you can ping the router from the file server. If possible, on the Router and the file server, try clearing the ARP cache. If you are using Windows Server 2003 as the router, you can run the following command (you can also run the following command on the file server): Netsh interface ip delete arpcache Otherwise, you may need to contact the vendor companies for this information. Best regards, Chang Yin

I reloaded the server with Windows 2003 and it works fine now. It is something in Win 2008. If I can load Win2003 with the defaults and get the share to work then it is not router or anything else. I still think another port is needed for communicating with 2008 but I don't know what that other port would be.

Hello, Just for your information, I can assure you that only port 445 is needed to redirect any access requesting to a shared folder on Windows Server 2008. I have done some tests on this. If I only add the port 445 redirection in the NAT server (running Windows Server 2003, and no other services or ports are selected), the access from external network to a Windows Server 2008 server in the internal network works well. Best Regards, Chang Yin

I'll ask our network management folks about that. Is that TCP or UDP?

Hi, It is still TCP, port 445. Best regards, Chang Yin