Network Between 2 Computers/Versatility

[KW7]

We have 2 desktop PC's, both of which connect to the Internet via Ethernet cable through our BT Versatility system.  They were networked together to enable file and printer sharing.  All was working fine until we had a visitor who wished to connect to the Internet wirelessly on an Ipad.  We called BT Versatility and they set up a wireless network to enable the visitor to access the Internet.  This worked for the visitor but almost immedialley afterwards we lost our own original network connection between the 2 computers and have been unable to re-establish it.  We have spoken to BT Versatility and to BT Broadband and neither of them have been of any help whatsoever and keep sending me round in circles.  Please can you advise how we can get the computers talking to each other again?  We have broadband connection - its just the network issue.  Thanks.

[TimDurham75]

I know nothing about BT Versatility but perhaps one of the following will help:

http://www.versatilitysystems.co.uk/manuals/BTV%20Broadband%20Module%20Manual%20Rev%202.pdf

http://www.best4systems.co.uk/_design/best4systems/_pdf/Systems/BT_Versatility/BT_Versatility_Intern...

I would not know how your internal lan was originally constructed but it seems likely, with only 2 PCs you would be using some form of simple peer-to-peer setup with "workgroup" or "homegroup" networking?  The IP configuration is important: IP addresses, network mask and gateway and how this is and was originally assigned: DHCP or static or possibly statically assigned via DHCP on the DHCP server (presumably the router).  The manner in which the machines resolve each other matters: this means DNS, HOSTS and LMHOSTS files possibly.  If it previously worked and then stopped then clearly something changed and I would imagine this might be the IP details (or possibly routing).  If you were peer-to-peer sharing then possibly the original details were static and may be recorded in local hosts and/or lmhosts files in windows\system32\drivers\etc folder.  If these contain entries that no longer match the current active IP details then you would probably fail to establish a network.

The clients should be able to ping each other by name - if that fails then can they ping by IP address?  In both cases, is this information holding the "expected" details - it needs to be consistent.  If the IP range has changed and, for example, does not match the named files content, if they exist, then you would not be able to connect.  Changing the appropriate mismatched information should then resolve the issue.

There are other factors too - routing and firewall configuration to name a couple... depending upon the configuration of these you might also be blocking traffic so a connection is not possible.

Don't know if that helps or makes sense to you (not knowing you technical level of knowledge) or even if it still matters, after 2 weeks but, as nobody had responded...

It seems likely the problem lies somewhere in that area but you do not actually provide much technical detail to go on...

For better assistance you would need to supply more information.  If BT were not able to help then it seems most likely that the issue lies client machine side and also involves the precise technicalities of the original setup.