Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General Discussion » View Thread |
Messages 1 to 10 of 14 total |
Wireless vs wired network |
Tue, Dec 1 2009 7:49 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Can anyone suggest an explanation for this?
I have a small network: 1 desktop and 3 notebooks. I recently wiped one of the notebooks and have reinstalled XP on it. Now, if it is connected to the other machines via cable it can see and access them all. If I try and use its wireless connection I still get internet access but can't access one of the other notebooks, but can the desktop and other notebook. I'm baffled. Roy Lambert |
Tue, Dec 1 2009 9:33 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I have a small network: 1 desktop and 3 notebooks. I recently wiped one of the notebooks and have reinstalled XP on it. Now, if it is connected to the other machines via cable it can see and access them all. If I try and use its wireless connection I still get internet access but can't access one of the other notebooks, but can the desktop and other notebook. >> Does the notebook that doesn't work have specific user account security set up for the shared resources ? If so, then the user security information may have changed on the wiped notebook, and you may need to re-setup the share security on the target notebook. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Dec 1 2009 10:26 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>Does the notebook that doesn't work have specific user account security set >up for the shared resources ? If so, then the user security information may >have changed on the wiped notebook, and you may need to re-setup the share Not as far as I'm aware, but who knows what MS do. I set up all my machines with the same user name (me) and password. My wife's is different - it user her name But even if your guess were right why when a bit of wire is used does it work and when no wire it doesn't? I also forgot to add I can go the other way Vista -> XP regardless of wired or wireless. Roy Lambert |
Tue, Dec 1 2009 10:55 AM | Permanent Link |
"Raul" | Silly question but I assume they're getting the same IP in both cases of
wired and wireless (i.e. from same router on same subnet ...). You did not specify what type of access you're trying to achieve but I assume file and printer sharing. First thing to check is if you can ping the inaccessible machine while on wireless - meaning that you have IP level communication and have problems further up the stack. If ping is OK then do you use AV/firewall software that might differentiate between wireless/wired ? It sounds like your other machine is Vista (which can be evil for sharing) but one thing to try is to setup the network connection type on that one as "Work network" - if you use Home then Vista tries to use IPv6 while work I found tends to work lot better in regular IPv4 intranetworking scenarios. Raul > But even if your guess were right why when a bit of wire is used does it > work and when no wire it doesn't? I also forgot to add I can go the other > way Vista -> XP regardless of wired or wireless. > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4651 (20091201) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com |
Tue, Dec 1 2009 12:13 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< But even if your guess were right why when a bit of wire is used does it work and when no wire it doesn't? I also forgot to add I can go the other way Vista -> XP regardless of wired or wireless. >> Yeah, good point. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Dec 2 2009 2:36 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Raul
>Silly question but I assume they're getting the same IP in both cases of >wired and wireless (i.e. from same router on same subnet ...). I also assume that >You did not specify what type of access you're trying to achieve but I >assume file and printer sharing. Yup >First thing to check is if you can ping the inaccessible machine while on >wireless - meaning that you have IP level communication and have problems >further up the stack. Good idea. I'll see >If ping is OK then do you use AV/firewall software that might differentiate >between wireless/wired ? Not as far as I know >It sounds like your other machine is Vista (which can be evil for sharing) >but one thing to try is to setup the network connection type on that one as >"Work network" - if you use Home then Vista tries to use IPv6 while work I >found tends to work lot better in regular IPv4 intranetworking scenarios. Good guess, and a very interesting observation. I'll have a go Roy Lambert |
Wed, Dec 2 2009 1:25 PM | Permanent Link |
"Raul" | >>First thing to check is if you can ping the inaccessible machine while on
>>wireless - meaning that you have IP level communication and have problems >>further up the stack. > > Good idea. I'll see The final thing I forgot to ask is how exactly are you are accessing the other PC - by name or by IP. If ping works but you can't access the share still and are using name then it might be worthwhile to try accessing it using IP as in "\\<ip>\<share name>" (e.g. \\1.2.3.4\myfiles). Raul __________ Information from ESET NOD32 Antivirus, version of virus signature database 4655 (20091202) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com |
Wed, Dec 2 2009 1:51 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Raul
>The final thing I forgot to ask is how exactly are you are accessing the >other PC - by name or by IP. Name >If ping works but you can't access the share still and are using name then >it might be worthwhile to try accessing it using IP as in "\\<ip>\<share >name>" (e.g. \\1.2.3.4\myfiles). It'll be the weekend at the earliest before I get a chance to mess about. The good news is that replacing the Vista m/c with an XP m/c seems to have improved the whole networking performance. I do wish I'd bought the XP upgrade with my main Vista notebook Roy Lambert |
Wed, Dec 2 2009 5:04 PM | Permanent Link |
"Jerry Clancy" | I agree with Raul's suggestion, ie, to setup the share with an IP instead of
the name (assuming you're not using DHCP). This was an issue (and solution) when mixing Win2000 and XP in our network. Jerry "Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:850B5AB6-0F0A-428A-A01B-51393444AF3A@news.elevatesoft.com... > Raul > >>The final thing I forgot to ask is how exactly are you are accessing the >>other PC - by name or by IP. > > Name > >>If ping works but you can't access the share still and are using name then >>it might be worthwhile to try accessing it using IP as in "\\<ip>\<share >>name>" (e.g. \\1.2.3.4\myfiles). > > It'll be the weekend at the earliest before I get a chance to mess about. > The good news is that replacing the Vista m/c with an XP m/c seems to have > improved the whole networking performance. I do wish I'd bought the XP > upgrade with my main Vista notebook > > Roy Lambert |
Wed, Dec 2 2009 5:31 PM | Permanent Link |
"Malcolm" | Jerry Clancy wrote:
> I agree with Raul's suggestion, ie, to setup the share with an IP > instead of the name (assuming you're not using DHCP). This was an > issue (and solution) when mixing Win2000 and XP in our network. > > Jerry If that works it is my (imperfect) understanding that it means the problem probably lies in Windows Name serving because IP addressing bypasses WINS .. or something like that. But if it all works on cable I think it most likely that the other laptop not playing ball can see a difference in the rebuilt machine and does not trust it. |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Wednesday, March 27, 2024 at 05:29 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |