32-bit TCP/IP Connection



Mary Jo
07-10-2005, 02:06 AM
I've published question below in the FrontPage discussion group and the only
answer they've come up with is to uninstall my firewall and then publish my
website updates.

As I would have to uninstall and re-install every time I publish that really
isn't a solution to the problem. I am on subscription service with McAfee so
it reall is out of the question not to mention that it leaves me exposed for
long periods of time which I don't like at all. I've never had a problem
publishing through my firewall until the past 30 days.

My operating system is WinXP Pro, FrontPage 2002

Any good suggestions from the Windows experts? I'm desperate. :-(


From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
> > Posted At: 18. maj 2005 07:04
> > Posted To: microsoft.public.frontpage.client
> > Conversation: TCP/IP Service Publishing Error
> > Subject: TCP/IP Service Publishing Error
> >
> >
> > Back Again,
> > Still receiving the error message using http: FrontPage
> > requires 32-bit TCP/IP connection to publish, this service
> > may not be installed or misconfigured.
> >
> > Have pinged myself and Yahoo.com with success. I cannot ping
> > my webites as
> > that capability is shut off at the host server. The host
> > service has tested
> > publishing to my sites with no problem so I think we can
> > cross that off the list. I have tested the Network service
> > through FrontPage and it tells me it is working properly. I
> > have used the detect & repair function in FP to no avail.
> >
> > My computer has no virus', spyware or trojans and all
> > security is running and up-to-date. MS Office is on SP-3 as
> > is my FP2002(stand alone). I have opened the TCP/IP service
> > to "allow full access" in my McAfee Firewall (though I was
> > always able to publish with "Outboound Access" only). I have
> > tried to publsih after disabling the firewall to no avail.
> >
> > I can't determine if this is a FrontPage problem or Windows
> > XP problem.
> >
> > Can someone please help, my sites are out of date and I am
> > under threat of having a critical link to one of them
> > disabled because of this problem

Brian Cryer
07-10-2005, 02:06 AM
I don't publish using FrontPage nor do I have experience using the McAfee
firewall, but these are just some ideas:

1. Can you publish if you have the McAfee firewall down? (Yes, I know this
isn't a good idea, but it does identify whether the problem lies with the
McAfee firewall or not.)

2. Assuming the problem is related tot he McAfee firewall then have a hunt
on their website or e-mail their technical support about the problem.

3. Assuming the problem is related to the McAfee firewall then remove the
McAfee firewall and either use the XP one (which is okay for stopping
inbound traffic but doesn't give you any warning of applications trying to
connect out), or try ZoneAlarm which I use without problem.

Hope this helps. Hope you get it going.

Brian

www.cryer.co.uk/brian

"Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
> I've published question below in the FrontPage discussion group and the
> only
> answer they've come up with is to uninstall my firewall and then publish
> my
> website updates.
>
> As I would have to uninstall and re-install every time I publish that
> really
> isn't a solution to the problem. I am on subscription service with McAfee
> so
> it reall is out of the question not to mention that it leaves me exposed
> for
> long periods of time which I don't like at all. I've never had a problem
> publishing through my firewall until the past 30 days.
>
> My operating system is WinXP Pro, FrontPage 2002
>
> Any good suggestions from the Windows experts? I'm desperate. :-(
>
>
> From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
>> > Posted At: 18. maj 2005 07:04
>> > Posted To: microsoft.public.frontpage.client
>> > Conversation: TCP/IP Service Publishing Error
>> > Subject: TCP/IP Service Publishing Error
>> >
>> >
>> > Back Again,
>> > Still receiving the error message using http: FrontPage
>> > requires 32-bit TCP/IP connection to publish, this service
>> > may not be installed or misconfigured.
>> >
>> > Have pinged myself and Yahoo.com with success. I cannot ping
>> > my webites as
>> > that capability is shut off at the host server. The host
>> > service has tested
>> > publishing to my sites with no problem so I think we can
>> > cross that off the list. I have tested the Network service
>> > through FrontPage and it tells me it is working properly. I
>> > have used the detect & repair function in FP to no avail.
>> >
>> > My computer has no virus', spyware or trojans and all
>> > security is running and up-to-date. MS Office is on SP-3 as
>> > is my FP2002(stand alone). I have opened the TCP/IP service
>> > to "allow full access" in my McAfee Firewall (though I was
>> > always able to publish with "Outboound Access" only). I have
>> > tried to publsih after disabling the firewall to no avail.
>> >
>> > I can't determine if this is a FrontPage problem or Windows
>> > XP problem.
>> >
>> > Can someone please help, my sites are out of date and I am
>> > under threat of having a critical link to one of them
>> > disabled because of this problem

Mary Jo
07-10-2005, 02:06 AM
Brian,
Thanks for answering so quickly.

I was on live chat for 45 minutes last night with McAfee and their only
answer or workaround is to uninstall and reinstall the firewall every time I
publish. Not a solution and will utlimately cause me more problems than I
have right now.

They had me allow blocked or limited access applications full access through
the firewall which I have NEVER had to do. I can't publish either via http or
ftp even with the firewall disabled. I have been to the FP discussion group
and several other trusted computer discussion groups to no avail. I've lost
a huge advertising opportunity to promote an event that will occur tomorrow
(5/20) because of this problem.

I can ping myself and Yahoo.com(which allows pinging). I cannot ping my
webistes as that ability is shut off at the host server. My hosting company
(The Host Group) has been able to test publish to the sites. I can access
anything on the web with no problem.

I am on a paid up subscription service with McAfee and have been for 2 years
and never had a problem until the past 30 days. This is nuts.

Here is my error message exactly:

Unable to open 'http://www.funkdujour.com.'
Server error: Accessing HTTP servers requires 32-bit TCP/IP Networking which
is not installed or may be misconfigured.
Possible causes:
1. The web server may not have the FrontPage Server Extensions installed. -
Yes it does
2. The web server may be temporarily our of service. - The sites are up and
running and I can access the Administration page on the host for each
3. If you are connecting through a proxy server, the proxy settings may be
incorrect. - Not using proxy, not turned on
3. An error may have occurred in the web server. - The hosting company has
not probelm test publishing
If this server does not support the FrontPage Server Extension(it does and
they are installed), FrontPage may still be able to publish to the server via
FTP. - I cannot publish via FTP at all right now.

Is there any way I can actually find out for sure if I have 32-bit TCP/IP
services running on my machine or something else such as just 16-bit services?




"Brian Cryer" wrote:

> I don't publish using FrontPage nor do I have experience using the McAfee
> firewall, but these are just some ideas:
>
> 1. Can you publish if you have the McAfee firewall down? (Yes, I know this
> isn't a good idea, but it does identify whether the problem lies with the
> McAfee firewall or not.)
>
> 2. Assuming the problem is related tot he McAfee firewall then have a hunt
> on their website or e-mail their technical support about the problem.
>
> 3. Assuming the problem is related to the McAfee firewall then remove the
> McAfee firewall and either use the XP one (which is okay for stopping
> inbound traffic but doesn't give you any warning of applications trying to
> connect out), or try ZoneAlarm which I use without problem.
>
> Hope this helps. Hope you get it going.
>
> Brian
>
> www.cryer.co.uk/brian
>
> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
> > I've published question below in the FrontPage discussion group and the
> > only
> > answer they've come up with is to uninstall my firewall and then publish
> > my
> > website updates.
> >
> > As I would have to uninstall and re-install every time I publish that
> > really
> > isn't a solution to the problem. I am on subscription service with McAfee
> > so
> > it reall is out of the question not to mention that it leaves me exposed
> > for
> > long periods of time which I don't like at all. I've never had a problem
> > publishing through my firewall until the past 30 days.
> >
> > My operating system is WinXP Pro, FrontPage 2002
> >
> > Any good suggestions from the Windows experts? I'm desperate. :-(
> >
> >
> > From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
> >> > Posted At: 18. maj 2005 07:04
> >> > Posted To: microsoft.public.frontpage.client
> >> > Conversation: TCP/IP Service Publishing Error
> >> > Subject: TCP/IP Service Publishing Error
> >> >
> >> >
> >> > Back Again,
> >> > Still receiving the error message using http: FrontPage
> >> > requires 32-bit TCP/IP connection to publish, this service
> >> > may not be installed or misconfigured.
> >> >
> >> > Have pinged myself and Yahoo.com with success. I cannot ping
> >> > my webites as
> >> > that capability is shut off at the host server. The host
> >> > service has tested
> >> > publishing to my sites with no problem so I think we can
> >> > cross that off the list. I have tested the Network service
> >> > through FrontPage and it tells me it is working properly. I
> >> > have used the detect & repair function in FP to no avail.
> >> >
> >> > My computer has no virus', spyware or trojans and all
> >> > security is running and up-to-date. MS Office is on SP-3 as
> >> > is my FP2002(stand alone). I have opened the TCP/IP service
> >> > to "allow full access" in my McAfee Firewall (though I was
> >> > always able to publish with "Outboound Access" only). I have
> >> > tried to publsih after disabling the firewall to no avail.
> >> >
> >> > I can't determine if this is a FrontPage problem or Windows
> >> > XP problem.
> >> >
> >> > Can someone please help, my sites are out of date and I am
> >> > under threat of having a critical link to one of them
> >> > disabled because of this problem
>
>
>

Brian Cryer
07-10-2005, 02:07 AM
Mary,

My hope was that it might not be the firewall that was causing a problem,
but having researched a bit and given your response that does seem to be the
most likely culprit. (I assume you've seen the microsoft article
http://support.microsoft.com/?kbid=265032, which isn't very helpful.)

In answer to your closing point, unless you are using Windows 3.1 or
possibly Windows 95, then you will be using 32-bit TCP/IP. I'm not sure
whether the reference is to 32bit drivers or 32bit TCP/IP - as opposed to
the 64 bit standard that is coming along. On that thought, something to
check - if you open your network connections and select your dial-up
connection (or local area connection or whichever connection you use to
connect to the internet), open up its properties, check that you have
"Internet Protocol (TCP/IP)" listed - I'm sure you do, but if you ONLY have
"Microsoft TCP/IP version 6" installed but not "Internet Protocol (TCP/IP)"
then that might be the problem. (Just seen in your original post that you
are using XP.)

Can I confirm that you can publish if you uninstall your firewall?

Just a thought, but given that you are using XP and Microsoft have made a
big thing about them now automating the download of service pack 2 - whether
you have service pack 2 or not, does XP think that the windows firewall is
on? Worth a quick check, given that you are using one from McAfee make sure
the XP one is off (because SP2 turns it on).

Don't have any other ideas, and couldn't find anything definitive on google.
If I have any other ideas I'll let you know.

Brian.

www.cryer.co.uk/brian



"Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
news:3356C1D0-70E9-4021-A156-E9A80A8CEC10@microsoft.com...
> Brian,
> Thanks for answering so quickly.
>
> I was on live chat for 45 minutes last night with McAfee and their only
> answer or workaround is to uninstall and reinstall the firewall every time
> I
> publish. Not a solution and will utlimately cause me more problems than I
> have right now.
>
> They had me allow blocked or limited access applications full access
> through
> the firewall which I have NEVER had to do. I can't publish either via http
> or
> ftp even with the firewall disabled. I have been to the FP discussion
> group
> and several other trusted computer discussion groups to no avail. I've
> lost
> a huge advertising opportunity to promote an event that will occur
> tomorrow
> (5/20) because of this problem.
>
> I can ping myself and Yahoo.com(which allows pinging). I cannot ping my
> webistes as that ability is shut off at the host server. My hosting
> company
> (The Host Group) has been able to test publish to the sites. I can access
> anything on the web with no problem.
>
> I am on a paid up subscription service with McAfee and have been for 2
> years
> and never had a problem until the past 30 days. This is nuts.
>
> Here is my error message exactly:
>
> Unable to open 'http://www.funkdujour.com.'
> Server error: Accessing HTTP servers requires 32-bit TCP/IP Networking
> which
> is not installed or may be misconfigured.
> Possible causes:
> 1. The web server may not have the FrontPage Server Extensions
> installed. -
> Yes it does
> 2. The web server may be temporarily our of service. - The sites are up
> and
> running and I can access the Administration page on the host for each
> 3. If you are connecting through a proxy server, the proxy settings may be
> incorrect. - Not using proxy, not turned on
> 3. An error may have occurred in the web server. - The hosting company has
> not probelm test publishing
> If this server does not support the FrontPage Server Extension(it does and
> they are installed), FrontPage may still be able to publish to the server
> via
> FTP. - I cannot publish via FTP at all right now.
>
> Is there any way I can actually find out for sure if I have 32-bit TCP/IP
> services running on my machine or something else such as just 16-bit
> services?
>
>
>
>
> "Brian Cryer" wrote:
>
>> I don't publish using FrontPage nor do I have experience using the McAfee
>> firewall, but these are just some ideas:
>>
>> 1. Can you publish if you have the McAfee firewall down? (Yes, I know
>> this
>> isn't a good idea, but it does identify whether the problem lies with the
>> McAfee firewall or not.)
>>
>> 2. Assuming the problem is related tot he McAfee firewall then have a
>> hunt
>> on their website or e-mail their technical support about the problem.
>>
>> 3. Assuming the problem is related to the McAfee firewall then remove the
>> McAfee firewall and either use the XP one (which is okay for stopping
>> inbound traffic but doesn't give you any warning of applications trying
>> to
>> connect out), or try ZoneAlarm which I use without problem.
>>
>> Hope this helps. Hope you get it going.
>>
>> Brian
>>
>> www.cryer.co.uk/brian
>>
>> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
>> news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
>> > I've published question below in the FrontPage discussion group and the
>> > only
>> > answer they've come up with is to uninstall my firewall and then
>> > publish
>> > my
>> > website updates.
>> >
>> > As I would have to uninstall and re-install every time I publish that
>> > really
>> > isn't a solution to the problem. I am on subscription service with
>> > McAfee
>> > so
>> > it reall is out of the question not to mention that it leaves me
>> > exposed
>> > for
>> > long periods of time which I don't like at all. I've never had a
>> > problem
>> > publishing through my firewall until the past 30 days.
>> >
>> > My operating system is WinXP Pro, FrontPage 2002
>> >
>> > Any good suggestions from the Windows experts? I'm desperate. :-(
>> >
>> >
>> > From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
>> >> > Posted At: 18. maj 2005 07:04
>> >> > Posted To: microsoft.public.frontpage.client
>> >> > Conversation: TCP/IP Service Publishing Error
>> >> > Subject: TCP/IP Service Publishing Error
>> >> >
>> >> >
>> >> > Back Again,
>> >> > Still receiving the error message using http: FrontPage
>> >> > requires 32-bit TCP/IP connection to publish, this service
>> >> > may not be installed or misconfigured.
>> >> >
>> >> > Have pinged myself and Yahoo.com with success. I cannot ping
>> >> > my webites as
>> >> > that capability is shut off at the host server. The host
>> >> > service has tested
>> >> > publishing to my sites with no problem so I think we can
>> >> > cross that off the list. I have tested the Network service
>> >> > through FrontPage and it tells me it is working properly. I
>> >> > have used the detect & repair function in FP to no avail.
>> >> >
>> >> > My computer has no virus', spyware or trojans and all
>> >> > security is running and up-to-date. MS Office is on SP-3 as
>> >> > is my FP2002(stand alone). I have opened the TCP/IP service
>> >> > to "allow full access" in my McAfee Firewall (though I was
>> >> > always able to publish with "Outboound Access" only). I have
>> >> > tried to publsih after disabling the firewall to no avail.
>> >> >
>> >> > I can't determine if this is a FrontPage problem or Windows
>> >> > XP problem.
>> >> >
>> >> > Can someone please help, my sites are out of date and I am
>> >> > under threat of having a critical link to one of them
>> >> > disabled because of this problem
>>
>>
>>

Mary Jo
07-10-2005, 02:07 AM
Thanks Brian,
SP2 hasn't been forced on me yet and I do not have the XP Firewall turned
on, I did check that previously. I'm trying to get this fixed before I
install SP2 (I have the disk from MS), because of the websies, I'd rather do
it that way. I am on Windows auto update so I'm against the clock as I think
my SP2 blocker may have already been disabled anyway.

Now that I have more time this weekend, I'll try uninstalling my firewal and
publishing and I will check my network connections again I did just look at
the Windows components under Networking Services, it lists Simple TCP/IP with
0.0mb installed, could that be the problem??

I'll wait for your reply before uninstalling my firewall.

Thanks so much.

"Brian Cryer" wrote:

> Mary,
>
> My hope was that it might not be the firewall that was causing a problem,
> but having researched a bit and given your response that does seem to be the
> most likely culprit. (I assume you've seen the microsoft article
> http://support.microsoft.com/?kbid=265032, which isn't very helpful.)
>
> In answer to your closing point, unless you are using Windows 3.1 or
> possibly Windows 95, then you will be using 32-bit TCP/IP. I'm not sure
> whether the reference is to 32bit drivers or 32bit TCP/IP - as opposed to
> the 64 bit standard that is coming along. On that thought, something to
> check - if you open your network connections and select your dial-up
> connection (or local area connection or whichever connection you use to
> connect to the internet), open up its properties, check that you have
> "Internet Protocol (TCP/IP)" listed - I'm sure you do, but if you ONLY have
> "Microsoft TCP/IP version 6" installed but not "Internet Protocol (TCP/IP)"
> then that might be the problem. (Just seen in your original post that you
> are using XP.)
>
> Can I confirm that you can publish if you uninstall your firewall?
>
> Just a thought, but given that you are using XP and Microsoft have made a
> big thing about them now automating the download of service pack 2 - whether
> you have service pack 2 or not, does XP think that the windows firewall is
> on? Worth a quick check, given that you are using one from McAfee make sure
> the XP one is off (because SP2 turns it on).
>
> Don't have any other ideas, and couldn't find anything definitive on google.
> If I have any other ideas I'll let you know.
>
> Brian.
>
> www.cryer.co.uk/brian
>
>
>
> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> news:3356C1D0-70E9-4021-A156-E9A80A8CEC10@microsoft.com...
> > Brian,
> > Thanks for answering so quickly.
> >
> > I was on live chat for 45 minutes last night with McAfee and their only
> > answer or workaround is to uninstall and reinstall the firewall every time
> > I
> > publish. Not a solution and will utlimately cause me more problems than I
> > have right now.
> >
> > They had me allow blocked or limited access applications full access
> > through
> > the firewall which I have NEVER had to do. I can't publish either via http
> > or
> > ftp even with the firewall disabled. I have been to the FP discussion
> > group
> > and several other trusted computer discussion groups to no avail. I've
> > lost
> > a huge advertising opportunity to promote an event that will occur
> > tomorrow
> > (5/20) because of this problem.
> >
> > I can ping myself and Yahoo.com(which allows pinging). I cannot ping my
> > webistes as that ability is shut off at the host server. My hosting
> > company
> > (The Host Group) has been able to test publish to the sites. I can access
> > anything on the web with no problem.
> >
> > I am on a paid up subscription service with McAfee and have been for 2
> > years
> > and never had a problem until the past 30 days. This is nuts.
> >
> > Here is my error message exactly:
> >
> > Unable to open 'http://www.funkdujour.com.'
> > Server error: Accessing HTTP servers requires 32-bit TCP/IP Networking
> > which
> > is not installed or may be misconfigured.
> > Possible causes:
> > 1. The web server may not have the FrontPage Server Extensions
> > installed. -
> > Yes it does
> > 2. The web server may be temporarily our of service. - The sites are up
> > and
> > running and I can access the Administration page on the host for each
> > 3. If you are connecting through a proxy server, the proxy settings may be
> > incorrect. - Not using proxy, not turned on
> > 3. An error may have occurred in the web server. - The hosting company has
> > not probelm test publishing
> > If this server does not support the FrontPage Server Extension(it does and
> > they are installed), FrontPage may still be able to publish to the server
> > via
> > FTP. - I cannot publish via FTP at all right now.
> >
> > Is there any way I can actually find out for sure if I have 32-bit TCP/IP
> > services running on my machine or something else such as just 16-bit
> > services?
> >
> >
> >
> >
> > "Brian Cryer" wrote:
> >
> >> I don't publish using FrontPage nor do I have experience using the McAfee
> >> firewall, but these are just some ideas:
> >>
> >> 1. Can you publish if you have the McAfee firewall down? (Yes, I know
> >> this
> >> isn't a good idea, but it does identify whether the problem lies with the
> >> McAfee firewall or not.)
> >>
> >> 2. Assuming the problem is related tot he McAfee firewall then have a
> >> hunt
> >> on their website or e-mail their technical support about the problem.
> >>
> >> 3. Assuming the problem is related to the McAfee firewall then remove the
> >> McAfee firewall and either use the XP one (which is okay for stopping
> >> inbound traffic but doesn't give you any warning of applications trying
> >> to
> >> connect out), or try ZoneAlarm which I use without problem.
> >>
> >> Hope this helps. Hope you get it going.
> >>
> >> Brian
> >>
> >> www.cryer.co.uk/brian
> >>
> >> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> >> news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
> >> > I've published question below in the FrontPage discussion group and the
> >> > only
> >> > answer they've come up with is to uninstall my firewall and then
> >> > publish
> >> > my
> >> > website updates.
> >> >
> >> > As I would have to uninstall and re-install every time I publish that
> >> > really
> >> > isn't a solution to the problem. I am on subscription service with
> >> > McAfee
> >> > so
> >> > it reall is out of the question not to mention that it leaves me
> >> > exposed
> >> > for
> >> > long periods of time which I don't like at all. I've never had a
> >> > problem
> >> > publishing through my firewall until the past 30 days.
> >> >
> >> > My operating system is WinXP Pro, FrontPage 2002
> >> >
> >> > Any good suggestions from the Windows experts? I'm desperate. :-(
> >> >
> >> >
> >> > From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
> >> >> > Posted At: 18. maj 2005 07:04
> >> >> > Posted To: microsoft.public.frontpage.client
> >> >> > Conversation: TCP/IP Service Publishing Error
> >> >> > Subject: TCP/IP Service Publishing Error
> >> >> >
> >> >> >
> >> >> > Back Again,
> >> >> > Still receiving the error message using http: FrontPage
> >> >> > requires 32-bit TCP/IP connection to publish, this service
> >> >> > may not be installed or misconfigured.
> >> >> >
> >> >> > Have pinged myself and Yahoo.com with success. I cannot ping
> >> >> > my webites as
> >> >> > that capability is shut off at the host server. The host
> >> >> > service has tested
> >> >> > publishing to my sites with no problem so I think we can
> >> >> > cross that off the list. I have tested the Network service
> >> >> > through FrontPage and it tells me it is working properly. I
> >> >> > have used the detect & repair function in FP to no avail.
> >> >> >
> >> >> > My computer has no virus', spyware or trojans and all
> >> >> > security is running and up-to-date. MS Office is on SP-3 as
> >> >> > is my FP2002(stand alone). I have opened the TCP/IP service
> >> >> > to "allow full access" in my McAfee Firewall (though I was
> >> >> > always able to publish with "Outboound Access" only). I have
> >> >> > tried to publsih after disabling the firewall to no avail.
> >> >> >
> >> >> > I can't determine if this is a FrontPage problem or Windows
> >> >> > XP problem.
> >> >> >
> >> >> > Can someone please help, my sites are out of date and I am
> >> >> > under threat of having a critical link to one of them
> >> >> > disabled because of this problem
> >>
> >>
> >>
>
>
>

Brian Cryer
07-10-2005, 02:09 AM
Mary,

just back from the weekend. How did you get on uninstalling your firewall
and trying again?

You said: "I did just look at the Windows components under Networking
Services, it lists Simple TCP/IP with 0.0mb installed, could that be the
problem??"

can I confirm where you are looking. This is where I would look to confirm
network settings:

Start > Control Panel (classic view) > Network Connections
Right click whichever connection you use to connect to the internet
(Local Area Connection in my case), and select Propreties.

On the general tab I have listed "Client For Microsoft Networks", "File and
Printer Sharing for Microsoft Networks", "QoS Packet Schedular" and
"Internet Protocol (TCP/IP)" listed. It is the last of these that I would
look for, just to check its listed (and not "Microsoft TCP/IP version 6" -
although its only a guess that the later TCP/IP driver could cause a
problem).

I've just found where you would see "Simple TCP/IP Services". This is under
which windows components you have installed. On my pc I have "Simple TCP/IP
Services" unchecked (and 0.0 MB). So, I don't believe that to be the
problem.

regards,

Brian.


"Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
news:8CB046C4-0AAC-4BFF-9425-55C72A119BDC@microsoft.com...
> Thanks Brian,
> SP2 hasn't been forced on me yet and I do not have the XP Firewall turned
> on, I did check that previously. I'm trying to get this fixed before I
> install SP2 (I have the disk from MS), because of the websies, I'd rather
> do
> it that way. I am on Windows auto update so I'm against the clock as I
> think
> my SP2 blocker may have already been disabled anyway.
>
> Now that I have more time this weekend, I'll try uninstalling my firewal
> and
> publishing and I will check my network connections again I did just look
> at
> the Windows components under Networking Services, it lists Simple TCP/IP
> with
> 0.0mb installed, could that be the problem??
>
> I'll wait for your reply before uninstalling my firewall.
>
> Thanks so much.
>
> "Brian Cryer" wrote:
>
>> Mary,
>>
>> My hope was that it might not be the firewall that was causing a problem,
>> but having researched a bit and given your response that does seem to be
>> the
>> most likely culprit. (I assume you've seen the microsoft article
>> http://support.microsoft.com/?kbid=265032, which isn't very helpful.)
>>
>> In answer to your closing point, unless you are using Windows 3.1 or
>> possibly Windows 95, then you will be using 32-bit TCP/IP. I'm not sure
>> whether the reference is to 32bit drivers or 32bit TCP/IP - as opposed to
>> the 64 bit standard that is coming along. On that thought, something to
>> check - if you open your network connections and select your dial-up
>> connection (or local area connection or whichever connection you use to
>> connect to the internet), open up its properties, check that you have
>> "Internet Protocol (TCP/IP)" listed - I'm sure you do, but if you ONLY
>> have
>> "Microsoft TCP/IP version 6" installed but not "Internet Protocol
>> (TCP/IP)"
>> then that might be the problem. (Just seen in your original post that you
>> are using XP.)
>>
>> Can I confirm that you can publish if you uninstall your firewall?
>>
>> Just a thought, but given that you are using XP and Microsoft have made a
>> big thing about them now automating the download of service pack 2 -
>> whether
>> you have service pack 2 or not, does XP think that the windows firewall
>> is
>> on? Worth a quick check, given that you are using one from McAfee make
>> sure
>> the XP one is off (because SP2 turns it on).
>>
>> Don't have any other ideas, and couldn't find anything definitive on
>> google.
>> If I have any other ideas I'll let you know.
>>
>> Brian.
>>
>> www.cryer.co.uk/brian
>>
>>
>>
>> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
>> news:3356C1D0-70E9-4021-A156-E9A80A8CEC10@microsoft.com...
>> > Brian,
>> > Thanks for answering so quickly.
>> >
>> > I was on live chat for 45 minutes last night with McAfee and their only
>> > answer or workaround is to uninstall and reinstall the firewall every
>> > time
>> > I
>> > publish. Not a solution and will utlimately cause me more problems
>> > than I
>> > have right now.
>> >
>> > They had me allow blocked or limited access applications full access
>> > through
>> > the firewall which I have NEVER had to do. I can't publish either via
>> > http
>> > or
>> > ftp even with the firewall disabled. I have been to the FP discussion
>> > group
>> > and several other trusted computer discussion groups to no avail. I've
>> > lost
>> > a huge advertising opportunity to promote an event that will occur
>> > tomorrow
>> > (5/20) because of this problem.
>> >
>> > I can ping myself and Yahoo.com(which allows pinging). I cannot ping my
>> > webistes as that ability is shut off at the host server. My hosting
>> > company
>> > (The Host Group) has been able to test publish to the sites. I can
>> > access
>> > anything on the web with no problem.
>> >
>> > I am on a paid up subscription service with McAfee and have been for 2
>> > years
>> > and never had a problem until the past 30 days. This is nuts.
>> >
>> > Here is my error message exactly:
>> >
>> > Unable to open 'http://www.funkdujour.com.'
>> > Server error: Accessing HTTP servers requires 32-bit TCP/IP Networking
>> > which
>> > is not installed or may be misconfigured.
>> > Possible causes:
>> > 1. The web server may not have the FrontPage Server Extensions
>> > installed. -
>> > Yes it does
>> > 2. The web server may be temporarily our of service. - The sites are
>> > up
>> > and
>> > running and I can access the Administration page on the host for each
>> > 3. If you are connecting through a proxy server, the proxy settings may
>> > be
>> > incorrect. - Not using proxy, not turned on
>> > 3. An error may have occurred in the web server. - The hosting company
>> > has
>> > not probelm test publishing
>> > If this server does not support the FrontPage Server Extension(it does
>> > and
>> > they are installed), FrontPage may still be able to publish to the
>> > server
>> > via
>> > FTP. - I cannot publish via FTP at all right now.
>> >
>> > Is there any way I can actually find out for sure if I have 32-bit
>> > TCP/IP
>> > services running on my machine or something else such as just 16-bit
>> > services?
>> >
>> >
>> >
>> >
>> > "Brian Cryer" wrote:
>> >
>> >> I don't publish using FrontPage nor do I have experience using the
>> >> McAfee
>> >> firewall, but these are just some ideas:
>> >>
>> >> 1. Can you publish if you have the McAfee firewall down? (Yes, I know
>> >> this
>> >> isn't a good idea, but it does identify whether the problem lies with
>> >> the
>> >> McAfee firewall or not.)
>> >>
>> >> 2. Assuming the problem is related tot he McAfee firewall then have a
>> >> hunt
>> >> on their website or e-mail their technical support about the problem.
>> >>
>> >> 3. Assuming the problem is related to the McAfee firewall then remove
>> >> the
>> >> McAfee firewall and either use the XP one (which is okay for stopping
>> >> inbound traffic but doesn't give you any warning of applications
>> >> trying
>> >> to
>> >> connect out), or try ZoneAlarm which I use without problem.
>> >>
>> >> Hope this helps. Hope you get it going.
>> >>
>> >> Brian
>> >>
>> >> www.cryer.co.uk/brian
>> >>
>> >> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
>> >> news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
>> >> > I've published question below in the FrontPage discussion group and
>> >> > the
>> >> > only
>> >> > answer they've come up with is to uninstall my firewall and then
>> >> > publish
>> >> > my
>> >> > website updates.
>> >> >
>> >> > As I would have to uninstall and re-install every time I publish
>> >> > that
>> >> > really
>> >> > isn't a solution to the problem. I am on subscription service with
>> >> > McAfee
>> >> > so
>> >> > it reall is out of the question not to mention that it leaves me
>> >> > exposed
>> >> > for
>> >> > long periods of time which I don't like at all. I've never had a
>> >> > problem
>> >> > publishing through my firewall until the past 30 days.
>> >> >
>> >> > My operating system is WinXP Pro, FrontPage 2002
>> >> >
>> >> > Any good suggestions from the Windows experts? I'm desperate. :-(
>> >> >
>> >> >
>> >> > From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
>> >> >> > Posted At: 18. maj 2005 07:04
>> >> >> > Posted To: microsoft.public.frontpage.client
>> >> >> > Conversation: TCP/IP Service Publishing Error
>> >> >> > Subject: TCP/IP Service Publishing Error
>> >> >> >
>> >> >> >
>> >> >> > Back Again,
>> >> >> > Still receiving the error message using http: FrontPage
>> >> >> > requires 32-bit TCP/IP connection to publish, this service
>> >> >> > may not be installed or misconfigured.
>> >> >> >
>> >> >> > Have pinged myself and Yahoo.com with success. I cannot ping
>> >> >> > my webites as
>> >> >> > that capability is shut off at the host server. The host
>> >> >> > service has tested
>> >> >> > publishing to my sites with no problem so I think we can
>> >> >> > cross that off the list. I have tested the Network service
>> >> >> > through FrontPage and it tells me it is working properly. I
>> >> >> > have used the detect & repair function in FP to no avail.
>> >> >> >
>> >> >> > My computer has no virus', spyware or trojans and all
>> >> >> > security is running and up-to-date. MS Office is on SP-3 as
>> >> >> > is my FP2002(stand alone). I have opened the TCP/IP service
>> >> >> > to "allow full access" in my McAfee Firewall (though I was
>> >> >> > always able to publish with "Outboound Access" only). I have
>> >> >> > tried to publsih after disabling the firewall to no avail.
>> >> >> >
>> >> >> > I can't determine if this is a FrontPage problem or Windows
>> >> >> > XP problem.
>> >> >> >
>> >> >> > Can someone please help, my sites are out of date and I am
>> >> >> > under threat of having a critical link to one of them
>> >> >> > disabled because of this problem
>> >>
>> >>
>> >>
>>
>>
>>

Mary Jo
07-10-2005, 02:09 AM
Brian,
Hope your weekend went better than mine. Unfortunately ended up too busy to
try the uninstall on MCAfee yet.
Regarding my Network conncections though - first off, I use AOL on Dial-up
so here's what in my connections:
Dial -UP American Online - disconnected - Contextant SmartHSFi V92 56K
SVCamera - disconnected - Conextant SmartHSFi V92 56K
LAN or High-Speed Interet - Local Area Connection - Disabled - Intel(R)
Pro/100 VE Network...
On the LAN connction properties, the TCP/IP service is check marked.
When I right-click on AOL only the AOL connection setup screen pops-up.

I use AOL SE w/TopSpeed and have had no problems with it until now. I don't
use their free firewall (which is McAfee, by the way) because my subscription
hasn't run out yet, I do use the SP#M control and pop-up blocker, I don't
have the Microsoft XP Firewall turned on, I do use SpyBot S & D, AdAware SE
and recently installed Microsoft Anti-Spyware - this problem started before I
loaded the MS Anti-spyware. There are no virus', trojans, spyware on my
machine.

I've never understood why the AOL Dial-Up connection has always shown that
it's disconnected - that's one of the things about AOL I dislike - it's so
darn proprietary, I wish it would just setup with the operating system like a
good child should. And as you can probably guess, though it's showing
disconnected - I AM online right now. Makes you crazy.

Gotta get to my real job - I'll let you know when I get a chance to
uninstall the McAfee firewall.

"Brian Cryer" wrote:

> Mary,
>
> just back from the weekend. How did you get on uninstalling your firewall
> and trying again?
>
> You said: "I did just look at the Windows components under Networking
> Services, it lists Simple TCP/IP with 0.0mb installed, could that be the
> problem??"
>
> can I confirm where you are looking. This is where I would look to confirm
> network settings:
>
> Start > Control Panel (classic view) > Network Connections
> Right click whichever connection you use to connect to the internet
> (Local Area Connection in my case), and select Propreties.
>
> On the general tab I have listed "Client For Microsoft Networks", "File and
> Printer Sharing for Microsoft Networks", "QoS Packet Schedular" and
> "Internet Protocol (TCP/IP)" listed. It is the last of these that I would
> look for, just to check its listed (and not "Microsoft TCP/IP version 6" -
> although its only a guess that the later TCP/IP driver could cause a
> problem).
>
> I've just found where you would see "Simple TCP/IP Services". This is under
> which windows components you have installed. On my pc I have "Simple TCP/IP
> Services" unchecked (and 0.0 MB). So, I don't believe that to be the
> problem.
>
> regards,
>
> Brian.
>
>
> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> news:8CB046C4-0AAC-4BFF-9425-55C72A119BDC@microsoft.com...
> > Thanks Brian,
> > SP2 hasn't been forced on me yet and I do not have the XP Firewall turned
> > on, I did check that previously. I'm trying to get this fixed before I
> > install SP2 (I have the disk from MS), because of the websies, I'd rather
> > do
> > it that way. I am on Windows auto update so I'm against the clock as I
> > think
> > my SP2 blocker may have already been disabled anyway.
> >
> > Now that I have more time this weekend, I'll try uninstalling my firewal
> > and
> > publishing and I will check my network connections again I did just look
> > at
> > the Windows components under Networking Services, it lists Simple TCP/IP
> > with
> > 0.0mb installed, could that be the problem??
> >
> > I'll wait for your reply before uninstalling my firewall.
> >
> > Thanks so much.
> >
> > "Brian Cryer" wrote:
> >
> >> Mary,
> >>
> >> My hope was that it might not be the firewall that was causing a problem,
> >> but having researched a bit and given your response that does seem to be
> >> the
> >> most likely culprit. (I assume you've seen the microsoft article
> >> http://support.microsoft.com/?kbid=265032, which isn't very helpful.)
> >>
> >> In answer to your closing point, unless you are using Windows 3.1 or
> >> possibly Windows 95, then you will be using 32-bit TCP/IP. I'm not sure
> >> whether the reference is to 32bit drivers or 32bit TCP/IP - as opposed to
> >> the 64 bit standard that is coming along. On that thought, something to
> >> check - if you open your network connections and select your dial-up
> >> connection (or local area connection or whichever connection you use to
> >> connect to the internet), open up its properties, check that you have
> >> "Internet Protocol (TCP/IP)" listed - I'm sure you do, but if you ONLY
> >> have
> >> "Microsoft TCP/IP version 6" installed but not "Internet Protocol
> >> (TCP/IP)"
> >> then that might be the problem. (Just seen in your original post that you
> >> are using XP.)
> >>
> >> Can I confirm that you can publish if you uninstall your firewall?
> >>
> >> Just a thought, but given that you are using XP and Microsoft have made a
> >> big thing about them now automating the download of service pack 2 -
> >> whether
> >> you have service pack 2 or not, does XP think that the windows firewall
> >> is
> >> on? Worth a quick check, given that you are using one from McAfee make
> >> sure
> >> the XP one is off (because SP2 turns it on).
> >>
> >> Don't have any other ideas, and couldn't find anything definitive on
> >> google.
> >> If I have any other ideas I'll let you know.
> >>
> >> Brian.
> >>
> >> www.cryer.co.uk/brian
> >>
> >>
> >>
> >> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> >> news:3356C1D0-70E9-4021-A156-E9A80A8CEC10@microsoft.com...
> >> > Brian,
> >> > Thanks for answering so quickly.
> >> >
> >> > I was on live chat for 45 minutes last night with McAfee and their only
> >> > answer or workaround is to uninstall and reinstall the firewall every
> >> > time
> >> > I
> >> > publish. Not a solution and will utlimately cause me more problems
> >> > than I
> >> > have right now.
> >> >
> >> > They had me allow blocked or limited access applications full access
> >> > through
> >> > the firewall which I have NEVER had to do. I can't publish either via
> >> > http
> >> > or
> >> > ftp even with the firewall disabled. I have been to the FP discussion
> >> > group
> >> > and several other trusted computer discussion groups to no avail. I've
> >> > lost
> >> > a huge advertising opportunity to promote an event that will occur
> >> > tomorrow
> >> > (5/20) because of this problem.
> >> >
> >> > I can ping myself and Yahoo.com(which allows pinging). I cannot ping my
> >> > webistes as that ability is shut off at the host server. My hosting
> >> > company
> >> > (The Host Group) has been able to test publish to the sites. I can
> >> > access
> >> > anything on the web with no problem.
> >> >
> >> > I am on a paid up subscription service with McAfee and have been for 2
> >> > years
> >> > and never had a problem until the past 30 days. This is nuts.
> >> >
> >> > Here is my error message exactly:
> >> >
> >> > Unable to open 'http://www.funkdujour.com.'
> >> > Server error: Accessing HTTP servers requires 32-bit TCP/IP Networking
> >> > which
> >> > is not installed or may be misconfigured.
> >> > Possible causes:
> >> > 1. The web server may not have the FrontPage Server Extensions
> >> > installed. -
> >> > Yes it does
> >> > 2. The web server may be temporarily our of service. - The sites are
> >> > up
> >> > and
> >> > running and I can access the Administration page on the host for each
> >> > 3. If you are connecting through a proxy server, the proxy settings may
> >> > be
> >> > incorrect. - Not using proxy, not turned on
> >> > 3. An error may have occurred in the web server. - The hosting company
> >> > has
> >> > not probelm test publishing
> >> > If this server does not support the FrontPage Server Extension(it does
> >> > and
> >> > they are installed), FrontPage may still be able to publish to the
> >> > server
> >> > via
> >> > FTP. - I cannot publish via FTP at all right now.
> >> >
> >> > Is there any way I can actually find out for sure if I have 32-bit
> >> > TCP/IP
> >> > services running on my machine or something else such as just 16-bit
> >> > services?
> >> >
> >> >
> >> >
> >> >
> >> > "Brian Cryer" wrote:
> >> >
> >> >> I don't publish using FrontPage nor do I have experience using the
> >> >> McAfee
> >> >> firewall, but these are just some ideas:
> >> >>
> >> >> 1. Can you publish if you have the McAfee firewall down? (Yes, I know
> >> >> this
> >> >> isn't a good idea, but it does identify whether the problem lies with
> >> >> the
> >> >> McAfee firewall or not.)
> >> >>
> >> >> 2. Assuming the problem is related tot he McAfee firewall then have a
> >> >> hunt
> >> >> on their website or e-mail their technical support about the problem.
> >> >>
> >> >> 3. Assuming the problem is related to the McAfee firewall then remove
> >> >> the
> >> >> McAfee firewall and either use the XP one (which is okay for stopping
> >> >> inbound traffic but doesn't give you any warning of applications
> >> >> trying
> >> >> to
> >> >> connect out), or try ZoneAlarm which I use without problem.
> >> >>
> >> >> Hope this helps. Hope you get it going.
> >> >>
> >> >> Brian
> >> >>
> >> >> www.cryer.co.uk/brian
> >> >>
> >> >> "Mary Jo" <MaryJo@discussions.microsoft.com> wrote in message
> >> >> news:1911314F-55F8-40CB-825D-3959A77BAE4F@microsoft.com...
> >> >> > I've published question below in the FrontPage discussion group and
> >> >> > the
> >> >> > only
> >> >> > answer they've come up with is to uninstall my firewall and then
> >> >> > publish
> >> >> > my
> >> >> > website updates.
> >> >> >
> >> >> > As I would have to uninstall and re-install every time I publish
> >> >> > that
> >> >> > really
> >> >> > isn't a solution to the problem. I am on subscription service with
> >> >> > McAfee
> >> >> > so
> >> >> > it reall is out of the question not to mention that it leaves me
> >> >> > exposed
> >> >> > for
> >> >> > long periods of time which I don't like at all. I've never had a
> >> >> > problem
> >> >> > publishing through my firewall until the past 30 days.
> >> >> >
> >> >> > My operating system is WinXP Pro, FrontPage 2002
> >> >> >
> >> >> > Any good suggestions from the Windows experts? I'm desperate. :-(
> >> >> >
> >> >> >
> >> >> > From: Mary Jo [mailto:MaryJo@discussions.microsoft.com]
> >> >> >> > Posted At: 18. maj 2005 07:04
> >> >> >> > Posted To: microsoft.public.frontpage.client
> >> >> >> > Conversation: TCP/IP Service Publishing Error
> >> >> >> > Subject: TCP/IP Service Publishing Error
> >> >> >> >
> >> >> >> >
> >> >> >> > Back Again,
> >> >> >> > Still receiving the error message using http: FrontPage
> >> >> >> > requires 32-bit TCP/IP connection to publish, this service
> >> >> >> > may not be installed or misconfigured.
> >> >> >> >
> >> >> >> > Have pinged myself and Yahoo.com with success. I cannot ping
> >> >> >> > my webites as
> >> >> >> > that capability is shut off at the host server. The host
> >> >> >> > service has tested
> >> >> >> > publishing to my sites with no problem so I think we can
> >> >> >> > cross that off the list. I have tested the Network service
> >> >> >> > through FrontPage and it tells me it is working properly. I
> >> >> >> > have used the detect & repair function in FP to no avail.
> >> >> >> >
> >> >> >> > My computer has no virus', spyware or trojans and all
> >> >> >> > security is running and up-to-date. MS Office is on SP-3 as
> >> >> >> > is my FP2002(stand alone). I have opened the TCP/IP service
> >> >> >> > to "allow full access" in my McAfee Firewall (though I was
> >> >> >> > always able to publish with "Outboound Access" only). I have
> >> >> >> > tried to publsih after disabling the firewall to no avail.
> >> >> >> >
> >> >> >> > I can't determine if this is a FrontPage problem or Windows
> >> >> >> > XP problem.
> >> >> >> >
> >> >> >> > Can someone please help, my sites are out of date and I am
> >> >> >> > under threat of having a critical link to one of them
> >> >> >> > disabled because of this problem
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>


32-bit TCP/IP Connection