I have put a new D-Link DFE 538TX in my XP Pro SP2 system as I think there
was a problem with the old on board Marvell Yukon card. Everything seemed to
go well and the drivers were installed fine. However, even though the
settings are identical to the Marvell card (apart from using an assigned IP
address of 192.168.1.123 instead of 192.168.1.100) there seems to be no
packets being sent or received when I look at the status of the connection.
It all seems connected to the router fine and have been assigned the correct
address (looking at status/support) and a repair reports no problems.
Enabling or disabling the old Marvel NIC makes no difference.
I have tried various cables in case that is the problem, including known
good ones.
Am I looking at the new card being dodgy or is there something else I can
do. I do find networking a little mysterious!
On Nov 22, 4:45 pm, "JRS" <j...@xvensson.f9.co.uk> wrote:
> I have put a new D-Link DFE 538TX in my XP Pro SP2 system as I think there
> was a problem with the old on board Marvell Yukon card. Everything seemed to
> go well and the drivers were installed fine. However, even though the
> settings are identical to the Marvell card (apart from using an assigned IP
> address of 192.168.1.123 instead of 192.168.1.100) there seems to be no
> packets being sent or received when I look at the status of the connection.
>
> It all seems connected to the router fine and have been assigned the correct
> address (looking at status/support) and a repair reports no problems.
>
> Enabling or disabling the old Marvel NIC makes no difference.
>
> I have tried various cables in case that is the problem, including known
> good ones.
>
> Am I looking at the new card being dodgy or is there something else I can
> do. I do find networking a little mysterious!
>
> TIA
>
> Jon
What, if any, firewall software / anti-virus system do you have on
this PC?
"smlunatick" <yveslec@gmail.com> wrote in message
news:87f10036-a71d-4954-908a-7985ac54fb81@b15g2000hsa.googlegroups.com...
> On Nov 22, 4:45 pm, "JRS" <j...@xvensson.f9.co.uk> wrote:
>> I have put a new D-Link DFE 538TX in my XP Pro SP2 system as I think
>> there
>> was a problem with the old on board Marvell Yukon card. Everything seemed
>> to
>> go well and the drivers were installed fine. However, even though the
>> settings are identical to the Marvell card (apart from using an assigned
>> IP
>> address of 192.168.1.123 instead of 192.168.1.100) there seems to be no
>> packets being sent or received when I look at the status of the
>> connection.
>>
>> It all seems connected to the router fine and have been assigned the
>> correct
>> address (looking at status/support) and a repair reports no problems.
>>
>> Enabling or disabling the old Marvel NIC makes no difference.
>>
>> I have tried various cables in case that is the problem, including known
>> good ones.
>>
>> Am I looking at the new card being dodgy or is there something else I can
>> do. I do find networking a little mysterious!
>>
>> TIA
>>
>> Jon
>
> What, if any, firewall software / anti-virus system do you have on
> this PC?
NOD32 and Sygate but disabling them makes no difference
On Nov 23, 10:24 am, "JRS" <j...@xvensson.f9.co.uk> wrote:
> "smlunatick" <yves...@gmail.com> wrote in message
>
> news:87f10036-a71d-4954-908a-7985ac54fb81@b15g2000hsa.googlegroups.com...
>
>
>
>
>
> > On Nov 22, 4:45 pm, "JRS" <j...@xvensson.f9.co.uk> wrote:
> >> I have put a new D-Link DFE 538TX in my XP Pro SP2 system as I think
> >> there
> >> was a problem with the old on board Marvell Yukon card. Everything seemed
> >> to
> >> go well and the drivers were installed fine. However, even though the
> >> settings are identical to the Marvell card (apart from using an assigned
> >> IP
> >> address of 192.168.1.123 instead of 192.168.1.100) there seems to be no
> >> packets being sent or received when I look at the status of the
> >> connection.
>
> >> It all seems connected to the router fine and have been assigned the
> >> correct
> >> address (looking at status/support) and a repair reports no problems.
>
> >> Enabling or disabling the old Marvel NIC makes no difference.
>
> >> I have tried various cables in case that is the problem, including known
> >> good ones.
>
> >> Am I looking at the new card being dodgy or is there something else I can
> >> do. I do find networking a little mysterious!
>
> >> TIA
>
> >> Jon
>
> > What, if any, firewall software / anti-virus system do you have on
> > this PC?
>
> NOD32 and Sygate but disabling them makes no difference
>
> Jon- Hide quoted text -
>
> - Show quoted text -
It "sad" to say but some softwares (McAfee an Norton) seem to still
br active even after disabling them. Only by removing them will these
software(s) be really disabled. Not familiar with NOD32 or Sygate?
By "assigned", you mean that your router gave your PC an address or you
manually entered an address. Always try DHCP before assigning an address.
Check with Sygate and see if it defines settings by IP address or NIC.
Switch back to the old IP address and see what happens.
Remove Sygate [that's a bit on the old side and discontinued BTW] and try
again.
"smlunatick" wrote:
> On Nov 23, 10:24 am, "JRS" <j...@xvensson.f9.co.uk> wrote:
> > "smlunatick" <yves...@gmail.com> wrote in message
> >
> > news:87f10036-a71d-4954-908a-7985ac54fb81@b15g2000hsa.googlegroups.com...
> >
> >
> >
> >
> >
> > > On Nov 22, 4:45 pm, "JRS" <j...@xvensson.f9.co.uk> wrote:
> > >> I have put a new D-Link DFE 538TX in my XP Pro SP2 system as I think
> > >> there
> > >> was a problem with the old on board Marvell Yukon card. Everything seemed
> > >> to
> > >> go well and the drivers were installed fine. However, even though the
> > >> settings are identical to the Marvell card (apart from using an assigned
> > >> IP
> > >> address of 192.168.1.123 instead of 192.168.1.100) there seems to be no
> > >> packets being sent or received when I look at the status of the
> > >> connection.
> >
> > >> It all seems connected to the router fine and have been assigned the
> > >> correct
> > >> address (looking at status/support) and a repair reports no problems.
> >
> > >> Enabling or disabling the old Marvel NIC makes no difference.
> >
> > >> I have tried various cables in case that is the problem, including known
> > >> good ones.
> >
> > >> Am I looking at the new card being dodgy or is there something else I can
> > >> do. I do find networking a little mysterious!
> >
> > >> TIA
> >
> > >> Jon
> >
> > > What, if any, firewall software / anti-virus system do you have on
> > > this PC?
> >
> > NOD32 and Sygate but disabling them makes no difference
> >
> > Jon- Hide quoted text -
> >
> > - Show quoted text -
>
> It "sad" to say but some softwares (McAfee an Norton) seem to still
> br active even after disabling them. Only by removing them will these
> software(s) be really disabled. Not familiar with NOD32 or Sygate?
>
"Gis Bun" <GisBun@discussions.microsoft.com> wrote in message
news:6E758070-ACB8-4F3B-83CF-8C7A34BD1DDF@microsoft.com...
> By "assigned", you mean that your router gave your PC an address or you
> manually entered an address. Always try DHCP before assigning an address.
>
> Check with Sygate and see if it defines settings by IP address or NIC.
> Switch back to the old IP address and see what happens.
>
> Remove Sygate [that's a bit on the old side and discontinued BTW] and try
> again.
>
> "smlunatick" wrote:
>
>> On Nov 23, 10:24 am, "JRS" <j...@xvensson.f9.co.uk> wrote:
>> > "smlunatick" <yves...@gmail.com> wrote in message
>> >
>> > news:87f10036-a71d-4954-908a-7985ac54fb81@b15g2000hsa.googlegroups.com...
>> >
>> >
It seems to connect with an assigned address but not if I use DHCP.
I have removed Sygate and disabled windows firewall.
Then something weird with your DHCP server. Check that server in the event
logs for any errors. Verify the PC is not configured in the DHCP anywhere.
"JRS" wrote:
>
> "Gis Bun" <GisBun@discussions.microsoft.com> wrote in message
> news:6E758070-ACB8-4F3B-83CF-8C7A34BD1DDF@microsoft.com...
> > By "assigned", you mean that your router gave your PC an address or you
> > manually entered an address. Always try DHCP before assigning an address.
> >
> > Check with Sygate and see if it defines settings by IP address or NIC.
> > Switch back to the old IP address and see what happens.
> >
> > Remove Sygate [that's a bit on the old side and discontinued BTW] and try
> > again.
> >
> > "smlunatick" wrote:
> >
> >> On Nov 23, 10:24 am, "JRS" <j...@xvensson.f9.co.uk> wrote:
> >> > "smlunatick" <yves...@gmail.com> wrote in message
> >> >
> >> > news:87f10036-a71d-4954-908a-7985ac54fb81@b15g2000hsa.googlegroups.com...
> >> >
> >> >
>
> It seems to connect with an assigned address but not if I use DHCP.
>
> I have removed Sygate and disabled windows firewall.
>
> Jon
>
>
>
New NIC - Zero Packets 
Linear Mode
