What I would do JoJo, is...
Check the PCs networking settings appear to be correct.
Netbios over TCP (NBT) needs to be enabled but often isn't.
The Windows Networking Client and File and Print Sharing for Microsoft Networks, need to be installed and bound to the network interface. Sometimes they are not, as Windows file sharing can be quite the security risk.
Any firewall/internet security package on the PC, must be configured to allow Netbios on the local subnet. Off the top of my head, TCP/UDP 135 and TCP 137, 138, 139, 445. As an aside, border devices should be configured to block Netbios, as it carries all sorts of information you would probably rather not leak onto the internet.
Check the router sharing config appear to be correct.
In the depths of Lanman and WfWg peer to peer history, the Workgroup name was used as an authentication mechanism, so should be made the same across all peer devices sharing resources. Computer and Workgroup names can be 15 characters but 8 characters removes any chance of legacy incompatibility - i.e. some third party devices are still depending on MSDOS conventions.
When you are happy the network is configured as it should be configured.
Open a cmd prompt on the PC and use...
net view \\<Router LAN IP>
Which should produce a list of shares or a meaningful error message.
If you get an error message, let us know what it is.
Just be aware that above TCP/IP and Netbios, Windows Networking protocols are proprietary to M$. Router manufacturers roll their own version of Samba (a closed room reverse engineering, Open Source project) to support Windows Networking. There is usually a delay between M$ making changes that bork Samba and Samba catching up. With the stupidly thin margins on domestic routers (sub £200), manufacturers will often launch a new device in preference to fixing an old device, which broke after the last Windows update.
Some M$ client's do not work with some third party devices and that is the end of it.
| Quote |
| I'm wondering if installing Win7 would help? |
How's your sense of humour this morning?
To pass on an old joke and risk offending some members of the audience.
There are two types of IT support people.
The Support Analyst: Works methodically from symptom to cause, breaking down the problem logically at each stage, locating the pertinent documentation, comprehending the available information in the context of what is observed, until they have identified which buttons should be pressed, in the order they must be pressed, to correctly resolve the underlying fault.
The Support Monkey: Repeatedly presses buttons at random, until a pleasing display of coloured lights is produced.:grin
More seriously. Installing Win7 will put the networking config back to defaults, which may be enough to get the sharing working. Introducing WIn7 to the problem would introduce new variables and failure modes though. A scratch install of XP would also get back to defaults, with less complication and a greater chance of being compatible with an old Samba implementation. Whether either method will work, depends on the nature of the failure in the first place - The fault may be the symptom of one or other end being misconfigured, or the combination of the two ends being fundamentally incompatible.
A quick Google indicates you are far from the only person struggling to map a drive to the DGN2200. 'Don't bother!' Being a fairly common suggestion.
HTH
