Welcome to ISAserver.org

"Network not available" and various odd problems.

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 General] >> General >> "Network not available" and various odd problems.

Page: [1]

Message

<< Older Topic Newer Topic >>

"Network not available" and various odd probl... - 12.Dec.2006 11:11:18 AM

Rutger

Posts: 2
Joined: 20.Oct.2006
Status: offline

Hello all,

I have set up an ISA 2006 box that is part of a new domain running inside our existing network. As each classroom is migrated to XP, the machines will then be plugged into a new switch to join and talk to the new domain. When the XP machines sit on the new network, they need access to resources sat outside on the old servers. ISA is set up so that the new internal range is 192.168.0.0/16 and the external interface sits on the old network of 10.2.86.0. User data saved on the old network is then made available to users logging in to the new network (using the same credentials imported using ADMT) by running ViceVersa Pro to sync user files etc. A rule was created on ISA to allow SMB/CIFS data through from internal to External for this sync and also for other data that is mapped using logon scripts for each user. It has also been placed at the top of the rule list. At this point we discovered the first flaw in the set up.

When there were lots of users logged in to both networks i.e. during lessons, running a manual syncronisation of about 200Mb of data would usually result in ViceVersa erroring out with a "The network name is no longer available" message. The progress would vary between syncs and 95% of times would fail so it could not be pinned to a particular file or directory. There were no errors in either machines' event logs or any pointers from ISA as to what was causing the failures so I started looking at hardware. Network cards in each server were upgraded along with drivers (ISA also) cables checked and switches/negotiation speeds checked/changed, all to no avail. The only times when we could sync 90% successfully was when there were hardly any clients logged in after school. We then started chasing rogue NIC's and switches elsewhere with still no joy.

Out of desperation one day I put another NIC in the server doing the sync'ing on the new network and connected it directly to the old network. Tried a sync and it worked first time every time no matter how many users on the system. It appears then that this is an ISA problem. This is now becoming more and more apparent when more clients are trying to access mapped file shares through ISA onto the old network.

This is happening on a clean install of a brand new domain on two identical servers (ISA and Domain Controller) using Windows 2003 R2. I have trawled the net to find anything relating to this issue but it always points to network card negotiation speeds and never to anything product related. I know that this is not the best configuration to allow SMB/CIFS out of a firewall but this is how I want ISA to work for us until we have everything talking to the new network. It also seems to work quite well until the number of clients increases.

Does anyone know of anything simple I can try, a reg tweak or patch, or a different configuration that would enable us to achieve our requirements? Any help would be greatly appreciated.

Thanks in advance.

Post #: 1

Featured Links*

RE: "Network not available" and various odd p... - 15.Dec.2006 5:41:51 PM

tshinder

Posts: 47644
Joined: 10.Jan.2001
From: Texas
Status: offline

Make sure there is a route relationship between the source and destination network.

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to Rutger)

Post #: 2