I have an Microsoft Access database (.mdb)about 185MB on a Novell 4.12 server. The network was recently upgraded with new switches and routers. It now takes about 45 seconds to open the database verses 22 seconds if the client resides on the same VLAN as the server. File transfer from client to server is very fast. Everything has been checked, NIC duplex, routers and switches config, upgraded the Novell client, and everything you can think of. Does anyone know if there's any other settings on the Novell server that can be checked? May be its a bug with the Cisco IOS or IPX routing. A trouble ticket has been submitted to Cisco.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Slowness Opening MS Access database
- Thread starter haiway1
- Start date
If it opens ok/fast on the same VLAN, then it sounds like a routing issue, not something on the NetWare server side. So if you take the exact same client PC and connect it to the same VLAN as the server, everthing is ok? Or are you testing with two different client PCs?
Is the database opened via a mapped network drive or a UNC path? If it is via UNC, try it via a mapped drive.
R.Sobelman
Is the database opened via a mapped network drive or a UNC path? If it is via UNC, try it via a mapped drive.
R.Sobelman
- Thread starter
- #3
Yes, when the client is on the same VLAN as the server, the file opens fast. When the client in on a different VLAN than the server and going through a router, it is slow. It's just an Access .mdb file on the Novell server and the client is mapped to the Novell share, not UNC. Also, file tranfer using IPX is very fast? Tried everything, even replacing the server NIC. No errors reported on the server port.
I assume by "mapped to the Novell share" that you mean it is a mapping done in the NetWare login script to a specific volume and directory. If by "Novell share" you mean it is getting to Novell via a Gateway for NetWare Services on a Windows server, than that's a whole different story.
The only other thing I can think of is name resolution. Try adding the NetWare server name to the HOSTS file on the local PC (that's just a shot in the dark though).
R.Sobelman
The only other thing I can think of is name resolution. Try adding the NetWare server name to the HOSTS file on the local PC (that's just a shot in the dark though).
R.Sobelman
- Thread starter
- #5
I tried that too but did not make a difference. Actually, I'm just a network performance guy that was asked to assist in troubleshooting this problem. Other than that, there could be other changes made on the server that I do not know about. I will research some more for them. I noticed they are using Zenworks and I'll look into that. Thanks.
What speed/duplex are you running and is it forced on both switch and server? Also, what Service Pack is the server running?
No point looking at Zenworks if it's a LAN issue...
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
No point looking at Zenworks if it's a LAN issue...
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question
- Locked
- Question