MS Access Problem

Discussion in 'Software' started by rusty155, Jan 31, 2007.

  1. Sparky
    Highly Decorated Member Award 500 Likes Award

    Sparky Zettabyte Poster Moderator

    10,718
    543
    364
    Yeah, it does look like an issue with a switch or many even a couple of switches not behaving like they should. If possible I would uplink each of the last 3 switches to the first switch and not have all 3 of them through one uplink cable to switch one.
     
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) MS-900 AZ-900 Security+ Network+ A+
    WIP: Microsoft Certs
  2. rusty155

    rusty155 Bit Poster

    35
    0
    24
    Thanks for all of the input guys. I'm not sure that individually linking the last three switches to the first one will make any real difference as they are stack-linked and are effectively acting as one switch anyway???
     
    WIP: A+
  3. r.h.lee

    r.h.lee Gigabyte Poster

    1,011
    52
    105
    rusty155,

    Questions:
    1. Is this Access 2002 class based on a Microsoft Office Specialist - Access 2002 instructor led or self study book with student files?
    2. How many CALs do you have for your system?
    3. How are the CALs installed, per-server or per-seat?
    4. What model(s) are the 3Com switches?
    5. Have you read my friend's post who's encountered this exact same problem in the real world with a real client with real money involved? http://www.certforums.co.uk/forums/showthread.php?t=14918
     
    Certifications: MCSE, MCP+I, MCP, CCNA, A+
    WIP: CCDA
  4. rusty155

    rusty155 Bit Poster

    35
    0
    24
    Ok!! I've been able to spend some time on this problem and have discovered the following:

    First of all, the problem that I am having is not related to MS Access at all! I has just been highlighted by it due to the apparent sensitivity of Access to network issues.

    The problem actually lies with the 3COM switches. They are all Superstack 3 4200 series switches (4226T more specifically).

    They appear, for whatever reason, to be resetting themselves approx every 10-20 minutes. This is causing the workstations attached to them to drop off the network for about 10-15 secs before they pick up an address again.

    If I try to manage the switches through a web browser, I receive the error:

    "Error in SNMP read. Failed to get system information."

    I am then prevented from viewing / changing any settings for the switch.

    If I Telnet in, I am able to view most settings, and can reset to factory defaults. I have done this, which does not reslove the problem. I am not able however to view or change any settings with regard to the IP address. If I attempt to, the following error occurs:

    "Invalid option, or combination of options selected"

    Out of 12 3COM switches, across 3 separate cabinets, this occurs on 5 switches. The strange thing is, that the switches that I can manage are uplinked to at least one other 3COM switch. That is, the problem 3COM switches are either directly linked to the core switch, or pass through a non-3COM switch before the core.

    Another strange occurance with regard to the first stack of 4 switches in the diagram is that I can get in to the management of the 2nd, 3rd and 4th switches in the stack, and thus view the stack as a whole. I am however unable to view or change the device settings of the stack - just see an overview. Within this overview, I can see the IP Address of the switch that I have pulled up through the browser, but the other switches in the stack show an IP of 0.0.0.0. This is the case for the last 3 Switches in the stack - I recieve the snmp error if I try to open up the management page of the first switch in the stack.

    I am sorry for the bombardment!! - I have been looking into this for the past couple of days with an engineer sent from RM without much success. (He has never seen or heard of anything like this before!)

    I am severely stuck at this point, and sinking increasingly out of my depth!!

    As a further note, I have contacted 3COM who only offer support for 90 days after purchase, and are only able to assist via a paid support option which I really do not want to pursue at this time!! I cannot find anything of use on their knowledgebase either!

    HELP!!:cry: :cry: :cry: :cry: :cry:

    @r.h.lee - your link directs me to the top of this post?? The CALs are all covered as part of RM CC3.
     
    WIP: A+
  5. hbroomhall

    hbroomhall Petabyte Poster Gold Member

    6,624
    117
    224
    There are quite a few postings that I've found which seem to indicate similar errors.

    One suggestion seen was to change the 1000base links to 100base.
    A 3com page seemed to suggest some problems in certain conditions of use.
    Another posting said that things improved with a later version of firmware, but were only finaly fixed when they threw them out.

    I *assume* you have a full set of manuals/docs for them? And have upgraded the firmware to the latest?

    I used to like 3Com stuff, but changed my mind when a complete building full of 3Com switches gradualy went bad over a year.

    Harry.
     
    Certifications: ECDL A+ Network+ i-Net+
    WIP: Server+
  6. rusty155

    rusty155 Bit Poster

    35
    0
    24
    Thanks for all of the help.

    A firmware upgrade to all of the switches fixed the problem!:oops:

    Is there any reason that this problem would occur? - one day it was working fine, and the next chaos!!

    Thanks again!
     
    WIP: A+
  7. hbroomhall

    hbroomhall Petabyte Poster Gold Member

    6,624
    117
    224
    Probably - but it will be a pig to find with all those users.

    The usual reason for this is that the pattern of useage changed for some reason, and tickled the bug that the new firmware fixed.

    Harry.
     
    Certifications: ECDL A+ Network+ i-Net+
    WIP: Server+

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.