Questions

Why is my newly connected mapped drive disconnected after 1 second

Tags:
+
0 Votes
Locked

Why is my newly connected mapped drive disconnected after 1 second

mista1876
I have a windows 2003 server that acts as a file server for my domain. When ever another pc in the domain maps a drive to the file server the drive automatically shows up as disconnected. I can double click it and it will pull up the data. However as soon as I try and grab a file from the mapped drive I get an error:

Cannot copy xxx(filename). The specified network name is no longer available.

I have tried the following:
1. Replace NIC card
2. Open Netscreen firewall any to any
3. Eventhough it disconnects automatically I still tried the Microsoft kbs of lanmanserver disconnect timeout


I should mention this file server is located in the DMZ of our network. And if a computer located in the DMZ maps to it there is no issue. However it a computer in the Trust maps to it that's when the issue occurs. I thought it was a firewall issue but I opened the firewall open and still had the issue. I also made another server in the DMZ act as a file server and tested with a PC in the trust and there was no issue.

Clarifications

Rob Kuhn

Does the Event Viewer give you any additional info?

What happens if you move the server outside of the DMZ and back into the private/LAN side of the firewall? Does it still act the same?

Are both the servers you mentioned configured the same with the same applications and services running? And are both in the same domain/policy?

  • +
    0 Votes
    mista1876

    The event viewer doesn't have anything referencing the event. I checked all machines looking for different errors.

    I haven't tried to move the server into the trust or vice versa.

    Yes they are configured with the same services for the most part. Yes they are in the same domain/policy but as mention before they are on different subnets.

    ** I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors***

    That is the strange part of all of this.

    +
    0 Votes
    mista1876

    The event viewer doesn't have anything referencing the event. I checked all machines looking for different errors.

    I haven't tried to move the server into the trust or vice versa.

    Yes they are configured with the same services for the most part. Yes they are in the same domain/policy but as mention before they are on different subnets.

    ** I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors***

    That is the strange part of all of this.

    +
    0 Votes
    Rob Kuhn

    "I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors"

    Tested the other way around? Do you mean you took the server out of the DMZ and thing were working OK?

    Another thing you can try is to change the IP on that server, put it back in the DMZ, and see if the problem continues. If it doesn't then I would look for a policy, rule, ACL, etc. in your firewall that might be blocking that IP or range of IP.

    If the problem does continiue to happen even with a different IP then we have to look closer at the server itself.

    +
    0 Votes
    mista1876

    Rob,

    When I said the other way around I mean the following:

    1. Created a shared folder on the machine in the trust zone.
    2. Logged on to the server in the DMZ and mapped to the newly created shared folder on the trust and was able to transfer files with no issues
    3. I do believe the issue is with the Server itself like a security policy or something that is killing connections or something. The firewall is open right now between those server for testing purpose.

    +
    0 Votes
    mista1876

    Rob,

    I got it working after changing the IP. Do you think its a DNS issue?

    +
    0 Votes
    Rob Kuhn

    mista1876 -

    hm. it sure sounds like it could be a DNS thing. Do you also have a WINS server for legacy NetBIOS machines? If so check there too. In fact I would go through anything that handles name resolutoin (including your DHCP scopes).

    If all of your name servers look good and all client machines are working with the server and it's new IP address I'd say keep it as-is :)

    +
    0 Votes
    CharlieSpencer

    I have multiple users with drives that display as disconnected. They open without problem when the users tries to access them.

    +
    0 Votes
    mista1876

    It's not really disconnected because I can double click it and it opens right up. But when I go to transfer a file the errors pops up. If the file is less than 10MB the transfer will complete. But anything over that the error pops up.

    +
    0 Votes
    sean

    With the server being in the DMZ you are passing the traffic through your firewall, this could be where your issue is. Protocols like NetBios dont necessarily pass the firewall rule set. To test I would do a number of things, make sure you have a rule that allows all traffic to pass on the firewall - for now you can lock it down after it works. Alternatively move the server out of the DMZ for now and see if that works. I prefer the second option as you can then be sure that the server itself is not having issues.

    Hope that helps.

  • +
    0 Votes
    mista1876

    The event viewer doesn't have anything referencing the event. I checked all machines looking for different errors.

    I haven't tried to move the server into the trust or vice versa.

    Yes they are configured with the same services for the most part. Yes they are in the same domain/policy but as mention before they are on different subnets.

    ** I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors***

    That is the strange part of all of this.

    +
    0 Votes
    mista1876

    The event viewer doesn't have anything referencing the event. I checked all machines looking for different errors.

    I haven't tried to move the server into the trust or vice versa.

    Yes they are configured with the same services for the most part. Yes they are in the same domain/policy but as mention before they are on different subnets.

    ** I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors***

    That is the strange part of all of this.

    +
    0 Votes
    Rob Kuhn

    "I tested the other way around longing onto the file server and mapping to a drive on the machine in the trust zone and everything worked no disconnected drives or errors"

    Tested the other way around? Do you mean you took the server out of the DMZ and thing were working OK?

    Another thing you can try is to change the IP on that server, put it back in the DMZ, and see if the problem continues. If it doesn't then I would look for a policy, rule, ACL, etc. in your firewall that might be blocking that IP or range of IP.

    If the problem does continiue to happen even with a different IP then we have to look closer at the server itself.

    +
    0 Votes
    mista1876

    Rob,

    When I said the other way around I mean the following:

    1. Created a shared folder on the machine in the trust zone.
    2. Logged on to the server in the DMZ and mapped to the newly created shared folder on the trust and was able to transfer files with no issues
    3. I do believe the issue is with the Server itself like a security policy or something that is killing connections or something. The firewall is open right now between those server for testing purpose.

    +
    0 Votes
    mista1876

    Rob,

    I got it working after changing the IP. Do you think its a DNS issue?

    +
    0 Votes
    Rob Kuhn

    mista1876 -

    hm. it sure sounds like it could be a DNS thing. Do you also have a WINS server for legacy NetBIOS machines? If so check there too. In fact I would go through anything that handles name resolutoin (including your DHCP scopes).

    If all of your name servers look good and all client machines are working with the server and it's new IP address I'd say keep it as-is :)

    +
    0 Votes
    CharlieSpencer

    I have multiple users with drives that display as disconnected. They open without problem when the users tries to access them.

    +
    0 Votes
    mista1876

    It's not really disconnected because I can double click it and it opens right up. But when I go to transfer a file the errors pops up. If the file is less than 10MB the transfer will complete. But anything over that the error pops up.

    +
    0 Votes
    sean

    With the server being in the DMZ you are passing the traffic through your firewall, this could be where your issue is. Protocols like NetBios dont necessarily pass the firewall rule set. To test I would do a number of things, make sure you have a rule that allows all traffic to pass on the firewall - for now you can lock it down after it works. Alternatively move the server out of the DMZ for now and see if that works. I prefer the second option as you can then be sure that the server itself is not having issues.

    Hope that helps.